Intersect CMS Unleashed [2.4]

[PyroTech03]

1 hour ago, XFallSeane said:

Like i have said Login is synch to Wordpress and Server it's better to keep registration directly on client on this way at now (Api not work if server is down and if user want registered that don't allow us to send api request to the server and registration is only on Wordpress side).

Registering on client directly sounds good. I remember reading on your page though saying it would disable normal login/registration on the WordPress site though. I was just suggesting that you had a way to tell WordPress to associate your WordPress account with your intersect account afterwards for sites that are already established. Similar in a way you can connect your socials on sites.

 

Example, I have about 120 accounts on my WordPress site. According to what you have at https://intersect-connect.tk/intersect-management-wordpress-plugin/ you are saying default WordPress login/registration should be off.

 

By making the system where users can tell the plugin what their account is and then verify it, it would allow the default functionality of WordPress. Otherwise you're asking users who have established WP sites to stop their normal operation. And by that point, it's an easier decision for most to probably just install the CMS and get the shop functionality that way.

[XFallSeane]

1 hour ago, PyroTech03 said:

Registering on client directly sounds good. I remember reading on your page though saying it would disable normal login/registration on the WordPress site though. I was just suggesting that you had a way to tell WordPress to associate your WordPress account with your intersect account afterwards for sites that are already established. Similar in a way you can connect your socials on sites.

 

Example, I have about 120 accounts on my WordPress site. According to what you have at https://intersect-connect.tk/intersect-management-wordpress-plugin/ you are saying default WordPress login/registration should be off.

 

By making the system where users can tell the plugin what their account is and then verify it, it would allow the default functionality of WordPress. Otherwise you're asking users who have established WP sites to stop their normal operation. And by that point, it's an easier decision for most to probably just install the CMS and get the shop functionality that way.

This page is not updated ^^
I recently implemented a login system, so if you have a custom plugin for membership it should work ^^

[PyroTech03]

That solves my issues then! Looking forward to being able to try it out.

[DJKNITEX]

So no errors when importing the SQL but when I go to my localhost it just gives me the directory and doing localhost/public/index.html is giving me an error. Did I miss a step somewhere?

 

Following your guide on your site