Hi,
sorry but we does not provide any integration like this, so you should ask support to Membership Pro Team. I think you mean integration at http://membershipprodoc.joomservices.com/synchronize-profile-data (developerd by Membership Pro developers)

403 - Access Denied message

have you installed some Security tools like Admin Tools?

ok, probably this is due to Admin Tools, and it happen also without Easy Profile, so please try to follow these steps:
- Go to "Administration->Extensions->Admin Tools->Web Application Firewall->Configure WAF->Joomla! Feature Hardening Options" and set to No following parameters:
1) Disable editing backend users' properties
2) Disable creating / editing backend users from the frontend

Thanks, that was good advice, but it made no difference.

Attached is what User Manager looks like

can you please post me your site details to check this?
you can use the form below the reply in "Site Details" tab

Hi,
found and fixed the problem in dev site, I will explain how to solve also in live site

Problem:
In the recent releases of Easy Profile we have added a search feature also in backend (all fields marked for search are visible). Unfortunately if a field is not searchable this cause a error. Normally you cannot set fields like "Delimiters" as searchable.
In old release there was a bug, when you create a field (also for delimiter type) then you could set it as searchable field.

Solution
You need to change from DB search flag from 1 to 0 for field "Street Address for Free Brochures" (ID: 26).
Table: "#__jsn_fields"
Column: "search"

I logged into the database and changed it there and that worked.

You have no idea how much I appreciate your working with me on this Sunday or Monday depending on where you are located.

I also see that I need to update from 2.4.2 top 2.4.3. Will have to update that database entry again as well?

And one last thing. you guys set some of your CSS as !important in tabs.min.css and style.min.css. that makes it hard to override in template.css

Hi,

I also see that I need to update from 2.4.2 top 2.4.3. Will have to update that database entry again as well?

If problem in version 2.4.2 is gone then you can upgrade without any other steps.

And one last thing. you guys set some of your CSS as !important in tabs.min.css and style.min.css. that makes it hard to override in template.css

We will try to improve this in future but unfortunately we use bootstrap classes and without !important rule the layout can have problems with some template.

I understand, it was on;y two cases.

Some component builders allow site builders to create their own themes by checking for a folder templates/my-template/html/com_jsn/assets/css/ and then loading the css from there rather than from /comopnents/lcom_jsn/assets/css/. Requires an additional IF statement to load the css, but makes modifications less confusing. this way the !important flag can be used for some template which need their default css overriden and yet lets the developer override specific css in the templates/my-template/html/com_jsn/assets/css/ folder where they can have both regular version of the css files that they can minify as needed.

One more thing, I wonder why we still use bootstrap classes when we cave css display:flex and css display:grid?

Hi,

Some component builders allow site builders to create their own themes by checking for a folder templates/my-template/html/com_jsn/assets/css/ and then loading the css from there rather than from /comopnents/lcom_jsn/assets/css/

Joomla natively allow override only of PHP views files, but maybe in future we can implement something like this.

One more thing, I wonder why we still use bootstrap classes when we cave css display:flex and css display:grid?

It's simple, Joomla uses bootstrap classes and have APIs to load own bootstrap framework. So, all Joomla templates already have a Bootstrap CSS style included. This allow us to not put CSS to reset and restyle entire output to fit alla templates. Keep in mind that our component works for all Joomla 3.x versions (Joomla 3.0 use bootstrap 2) and it need to fit all templates(bootstrap 2 and 3 and in future also 4), so it's normal to use !important statement in some cases.
Of course the CSS code could be improved in future.

I know, but using bootstrap classes locks us into old technology.

It is much faster to allow the browser with it's compiled procedures to calculate column heights and widths rather then relying on Bootstrap JS to do it.

But maybe Bootstrap will adapt to the new css classes in the future and this will be a moot point.

I am already using the CSS display:flex property on some of my pages because it just adapts so well to all the devices.