Hi,
Can you make sure your permalink set to “Post name”? Also, there is ‘/’ at the end of the structure like “/%postname%/”?
Regards,
Patrik
Thread Starter
bward
(@bward)
Ahh, we do not have the trailing slash. We like to keep our URLs clean.
Is there another way we can accomplish this just for the URLs the plugin creates?
Plugin Contributor
Paolo
(@paoltaia)
Hi,
not having the trailing slash in your permalinks will break every 2nd level URLs like
/profile/username/.
or
/author/username/ which is what WordPress would output by default.
WordPress default behavior is to add a trailing slash at the end of URLs, removing it, unfortunately, won’t work.
Thank you
Thread Starter
bward
(@bward)
Appreciate the quick response Paolo.
Actually, that is not the case. We do not have the trailing slash and author URLs work fine. We have run the site this way for years. Other membership plugins work fine this way on our site as well, I only noticed this issue with this plugin.
No scripts I can add to functions?
Thanks sir!
Plugin Contributor
Paolo
(@paoltaia)
Sorry about that, I just double-checked and you are right, I asked @wpdev10 to follow up. He’ll let you know how to proceed asap.
Thanks
Thread Starter
bward
(@bward)
I sincerely appreciate you reaching out to your folks Paolo. Have a fantastic day sir.
Hi,
We have fixed this by adding a trailing slash to the URL. This change will be there in the next plugin update release.
Regards,
Patrik
Thread Starter
bward
(@bward)
Hey, thanks so much Patrik and team. I will keep an eye out for the update and test that one out. Really appreciate it.
My only other thought before making the switch. When UsersWP is activated, I see some requests for “use.fontawesome.com” on all pages. Is there a way to dequeue these so they only load on the pages they are required to run on?
We love keeping our pages lean and clean. Thank you.
Thread Starter
bward
(@bward)
Gents, attempting to add more information here. In addition to the styles, I ended up finding scripts running on pages where the plugin is not needed. Would love a way to dequeue these styles and scripts except when actually needed for a member-based page.
Styles:
Header font-awesome use.fontawesome.com https://use.fontawesome.com/releases/v5.14.0/css/all.css?wpfas=true
Header font-awesome-shims use.fontawesome.com https://use.fontawesome.com/releases/v5.14.0/css/v4-shims.css?wpfas=true
Header ayecode-ui stagin…ebible.temp927.kinsta.cloud wp-content/plugins/userswp/vendor/ayecode/wp-ayecode-ui/assets/css/ayecode-ui-compatibility.css
Scripts:
Header select2 stagin…ebible.temp927.kinsta.cloud wp-content/plugins/userswp/vendor/ayecode/wp-ayecode-ui/assets/js/select2.min.js
Header bootstrap-js-bundle stagin…ebible.temp927.kinsta.cloud wp-content/plugins/userswp/vendor/ayecode/wp-ayecode-ui/assets/js/bootstrap.bundle.min.js
Header userswp stagin…ebible.temp927.kinsta.cloud wp-content/plugins/userswp/assets/js/users-wp.min.js
Hi,
We load our assets on all pages because we have widgets which are used on other pages then members related pages so if we load on specific pages then those widgets and shortcodes will not display or work properly and that’s the reason we display our CSS and JS on all the pages of sites.
For fontawesome loading you can check our setting in backend Settings->Font Awesome.
Regards,
Patrik
