This topic has 9 replies, 4 voices, and was last updated 3 years, 1 months ago ago by Orange Sign
for a week now my theme options arent working itll just take me to a blank loading screen.
tried a lot of things
from deactivating most plugins clearing caches browse incognito.
change php versions
but nothing seems to solve the issue
Ive added ftp and wp credentials please have a look and tell me how i can solve this issue
Hi!
( Just participating )
I recently had the same kind of issue, concerning the blank page, and, Elementor widgets weren’t also opening.
For my case, increasing the php memory limit solved that blank page issue.
The server was set the 32M by default but raised to 512MB and it was ok.
define(‘WP_MEMORY_LIMIT’, ‘512M’);
Hope it can help.
Mario 🙂
thx mate!
also done
didnt solve a thing
I suspect it has something to do with no xstore folder being in wp-content/plugins
Oh wauw.
Why is it working on your end and not on any of the devices i use?
Hello,
Different members from our team checked your Theme Options on different devices and all works fine.
Please try the next:
– update your browser, like https://support.google.com/chrome/answer/95414?hl=en&co=GENIE.Platform%3DDesktop&oco=0
– disable extensions for browser https://support.google.com/chrome_webstore/answer/2664769?hl=en
– clear cache https://support.google.com/accounts/answer/32050?hl=en&co=GENIE.Platform%3DDesktop
Let us know the result.
Regards
Hi Rose,
Thanks for your reaction.
I did all of the above and still keep the same problem
What else could it be?
I ruled out a lot of problems:php version,server memory,browser,os
Kinda lost what else it could be Please help since im not able to do my work properly for over a week now.
Fixed it!!
switched to parent theme and it worked.
after a view adjustments to the layout of my page the same problem continues.
this time theme options are shown in theme preview.
but can no longer open them blank loading screen returns.:(
The issue related to '‘Xstore theme options fail to open’' has been successfully resolved, and the topic is now closed for further responses