Home › Forums › Weaver Xtreme Theme › Weaver Xtreme Plus is conflicting with the plugin
- This topic has 7 replies, 3 voices, and was last updated 1 month, 1 week ago by
Maggard_Manda.
-
AuthorPosts
-
October 26, 2023 at 13:35 UTC - Views: 35 #73553
Maggard_Manda
ParticipantOctober 26, 2023 at 13:57 UTC - Views: 32 #73554Maggard_Manda
ParticipantI found a work around. It appears that the SiteOrigin Editor is working and not conflicting with the Xtreme Plus plugin.
October 26, 2023 at 14:00 UTC - Views: 31 #73555User
ParticipantNope… all is working well….
Please kindly go to Weaver Xtreme Admin and copy out “Your System and Configuration Info” and post it here.
Neither the Weaver theme nor the plugin have been updated in the last few days, so those are unlikely to be the cause.
Regards!
October 26, 2023 at 14:26 UTC - Views: 28 #73556Maggard_Manda
ParticipantCan you tell me how to copy out my System and Configuration Info?
Weaver Xtreme Admin > Save/Restore > Download Current Settings to Your Computer? Is it Save All? Or Save Only Theme Related?
Is that the right place?
October 26, 2023 at 15:02 UTC - Views: 26 #73557scrambler
ModeratorHelp page > System Info box
can you elaborate on what error you get if any?
October 26, 2023 at 16:01 UTC - Views: 24 #73558User
ParticipantOctober 26, 2023 at 16:28 UTC - Views: 21 #73559Maggard_Manda
ParticipantI swapped out the Visual Editor for the SiteOrigin Editor because the whole tool box area of where you edit the font on the visual side had disappeared. This was in the widget area as well as all of the pages.
The SiteOrigin Editor worked in all of the widget areas, but as I’m working on the home page, I made an addition and click done and then UPDATE . But when I refresh the home page nothing takes. And when I go back into edit the page I get an error stating: “There is a newer version of this widget’s content available. RESTORE or DISMISS”. And even when I click restore my work comes back, but once I click UPDATE, it isn’t taking.
I’ve repeated this at least 5 times.
October 26, 2023 at 18:10 UTC - Views: 12 #73560Maggard_Manda
ParticipantWe now think it is the Black Studio TinyMCE Widget that is causing the errors. It hasn’t been updated for 1 year.
-
AuthorPosts
- You must be logged in to reply to this topic.