microsyskl

I have the same problem. I don’t even know what your plugin is doing on this site but If I update past 2.15 I lose navigation menu on top of ALL pages. I tried the add-on control you suggested in earlier thread but no idea where to start. I turned all off and one by one enabled them with no success. I reverted back to 2.15 until you guys come up with a better solution. THIS MUST BE FIXED.. PLEASE! Thank you

NOTE: I recommend users install ROLLBACK plugin to easily revert back to 2.15. Prior to this I had to do a restore and lost a lot of time on this!

Correct – Being Established in Righteousness is the latest series. I can order them properly on the sermons page ([sermon_images order=”DESC” orderby=”id” size=”sermon_medium”]) – but the footer widget stopped working when I moved to another server (using latest_series). I think the SQL file may have gotten corrupted because that alone will not sort properly.

I changed the short code without orderby with no success. BTW – I was trying every variation so that was probably fallout.

NOTE: It ‘was’ working fine before the migration last yr. ?

I am also experiencing the IDENTICAL problem. Tried everything!

Not sure if it is related but Yoast 12 and current version of WordPress crash the editor. I also am running Avada 6.x. Their editor works somewhat, but there are also inconsistencies there as well. The exact symptom i am experiencing is that I cannot open the WordPress default editor at all. I click the button but nothing happens.

THIS IS HAPPENING ON MULTIPLE SITES THAT I HOST with similar platform. Currently i have deactivated Yoast and I am able to edit both in WordPress as well as AVADA Fusion editor.

PLEASE HELP!

resolved now… ??

That seemed to do it! Thanks!! Disabling SSL Verification??

Strange thing is that i have another wp site hosted on same VPS Server and it works fine (with SSL enabled)??

Also, prior to disabling the SSL, I did run all the connectivity tests with your WordFence servers and it passed with no problem??

Oh well – it works so i will leave well enough alone!

No, that comes up and stops there in debug when I try to run the first scan after plugin install.

I turned debug on because it just hangs at … “Fetching core, theme and plugin file signatures from Wordfence”

In other words i cannot get a successful scan after a new install of your plugin