FYI: WPML String Translations plugin has a conflict with cornerstone. While activated cornerstone is unable to render the preview.
The well known message: The preview could not load due …" appears.
Deactivate the WPML plugin and all run just fine.
FYI: WPML String Translations plugin has a conflict with cornerstone. While activated cornerstone is unable to render the preview.
The well known message: The preview could not load due …" appears.
Deactivate the WPML plugin and all run just fine.
Hello @VRANKOVINA,
Thanks for writing to us.
I suggest you take a look at this thread to resolve your issue. If it doesn’t work for you, please share your details in a secure note. Please provide the following details
You can find the Secure Note button at the bottom of your posts
Thanks
Hello
Well. This option is unchecked.
anyway - see secure note pls.
EDIT: I tried both solutions: the mentioned option above unchecked and checked including the language path entered. I failed.
Hi Ondrej,
If you have already tried by checking the option shown in the reference thread given by my colleague, there might be some different reasons behind your issue. I would like to suggest troubleshooting the following common issue to help us recognize the reason.
1.Theme Related Issue
2.Plugin Conflict
3.Theme Update related issue
4.Child Theme Related issue
5.CSS/JS Customization
6.Disabling Cache
7.Disabling CDN
If you discover that an issue is coming from a custom code or 3rd third-party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins, unless you are subscribed to One. If not subscribed, kindly consult with a developer or contact the plugin author.
Please note that we do not provide support for custom codes and 3rd party plugins, unless you are subscribed to One service.
If none of the above helps, please copy your live site to a staging server so we can troubleshoot freely without breaking your live site.
And give us access to the secure note, including:
– WordPress Site URL & Login URL
– WordPress Admin username/password
To create a secure note, click the key icon underneath any of your posts.
Thanks
Staging is set up
Hi Ondrej,
Unfortunately, the staging site is showing the error.
Thanks
yep to many files. It reached the limit.
I’d need to do some cleanup first. He… I need this at the moment.
Hey Ondrej,
Just let us know when the staging site is ready.
Cheers.
This might be a fight against windmills because of the sheer number of files. The hosts limit is 180k files. I might free some space, but that won’t be enough, I’m afraid.
The site is running a shop, extensive user management, multilanguage, where shall I stop. Even there are some media files (a fair amount), those do not significantly participate to the files number.
In respect to the size in MB, it just needs like 20% of the space available… this is not an issue, by far not.
You may find an another thread I opened regarding font awesome. 30k+ svgs, folks, that is a lot, a lot of files. And this is I’ve found out recently, what else will I find?
If you have any hint, how to lower the file number, I’d appreciate very much. And I’m yet beyond the number of plugins and themes ;). Even there are some inactive plugins, I need them at the right time. As those seem to cause issues with cornerstone, I deactivate them, do the edits an activate back again, or not. Anyway right now I need to get rid of couple of 10k files…
Hello Ondrej,
Are you using SVG for Font Awesome? By default, the Font Awesome SVG files were placed inside a zip file. Once you have enabled SVG, the file will be unzipped automatically. If ever switched back to Webfont, the SVG files are already there. In this case, I highly recommend that you manually reinstall the Pro theme and ensure that you do not enable the Font Awesome SVG Load Type.
If the above does not apply to your site, then you manually remove the unnecessary SVG files. It can be found in wp-content/theme/pro/cornerstone/assets/svg/fontawesome.
Hope
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.