dt123

Hi. I too have found an issue since upgrading to PeepSo 3. Using WP-Debug I geet the following error on my pages https://staging.mysalus.org

Notice: peepso_navigation_profile: engagement-points *href* should be the same as *id* (points) in /var/www/vhosts/mysalus.org/staging.mysalus.org/wp-content/plugins/peepso-core/peepso.php on line 4243

Ideas?

Thank you

Thanks for checking. It does seem to be working now. Not sure what was going on.

Hi and than you for the quick response. I did make some changes earlier this morning that resolve many of the issues I mentioned – sorry just getting back to update ticket now.

The only other thing I could point out is that changing from WP Fastest Cache to W3 total cache seemed to make the difference, and the 404 errors I mentioned must have been a latency issue after switching caching plugins.

Any suggestions regarding the avoid css @import? – Not a biggie right now.

Thank you for your great plugin and support!

Hi all. I would like to revisit this ticket as I am not trying to deal with site performance and have noted that their are several SIQ related issues pointed out using GTMetrix including: Optimize the order of styles and scripts, Avoid bad requests (the urls generated by wp fastest cache? – even thought the plugin was deactivated before running the GTmetrix test), and Avoid CSS @import.

Looking at the waterfall report, these errors indicate that they are consuming around 2s of page load time!

Not sure why 404 urls as still in play if they are due to fastest cache and would think they/issues with SIQ would go away with fastest cache deactivated. I now have w3 total cache running to see if I can use it with SIQ but have not figured it out.

Any ideas on what to do next? Obviously I can’t have the 2s page load adds I am seeing with SIQ

Ideas from here?

Thank you

yes, i think so, doing more testing now. sorry for the dual posts.

please disregard

Please disregard.

OK. Thank you, will look forward to the new version update

Now however, that fix compromises the backend page/post editor. I confirmed trying with and without the commented line. With commented line the frontend modals work. On the backend the editor screen is messed up. Can send you a screenshot if you like and tell me how to get that to you.

thank you

Hi bhaldie. That fixed the issue! Should I just leave that link commented out?

Thank you

Thank you, will do

Thank for taking a look and yes, sorry – I had MD deactivated while further testing. Now have it activated and you can see behavior. Will leave it activated until I hear back from you.

Result is I can not activate the plugin and plan.

OK, thank you. I now have the menu item back! (didn’t knw I could just add back the caps). Will do others mentioned also.

Thanks so much for your help with this.

I jus don’t see that cap … only the mdocs_dashboard cap for administrator. I have 3.9.10 running. Can I just add the mdocs_allow_upload through user role editor? Guess I will try that.