I've just installed Flatsome theme version 3.11.0, wordpress 5.4, php 7.4, mysql 8.0 on my SSL protected site.
I disable all plugins, not even one.
First, I can edit home page easily. But when I edit other page, like contact, about... it was not loaded.
I checked console, has a error in image 1.
Uncaught TypeError: Cannot read property 'isRoot' of undefined
at t.value (editor.js?ver=3.11.0:2)
But I refreshed page while console opened, no error display in image 2.
That error only show when console closed.
Please help me, thank you so much.
I've faced this issue on various hosting platforms, and the solution has been different. Listing some of those here:
If you are using cloudflare, disable cache, preferably enable developer mode, while you are doing the edits
If you are using any caching plugin disable those
Ensure that you are using the same scheme (http vs https) to serve your site as has been added to your wp-config
Reload the page after you've disabled all cache
I had a similar problem, and between clearing the cache, and switching to the twenty Twenty theme the problem fixed itself.
Temporarily disable catche plugins and it would work.
Related
I am trying to move an existing site that works fine on the old server to a new server. On the new server the homepage is just showing blank page. however when i navigate to "wp-admin" or other pages like "about-us" shoiws up just fine and i am also able to login in my wp-admin. It's just the homepage that is blank..
I have tried to enable debug and also tried looking into wp_content/debug.php and it's empty:
define('WP_DEBUG',true);
define('WP_DEBUG_LOG',true);
define('WP_MEMORY_LIMIT','256M');
Next thing i tried is the permalink settings -> permalink -> "save" it also didn't work.
I have also tried by switching php version php7.3 same as the old server, didn't help
then finally i tried removing the plugins one by one and figured after removing this particular elementor plugin (https://www.eletemplator.com/ele-custom-skin/) the home page was loading fine. However this plugin is very important as most of the pages are using templates from this plugin to display the content.
Now that I know this plugin is causing the issue on the new server could it be because of the loading time? with this plugin on the old server everything works fine.
hope someone can help on this
For resolving this issue you can choose following steps:
1: First you try to disabling all the plugins of yours and then see if the front end comes back. If you can’t do it from the backend due to any reason, you can as well rename /plugins/ folder to /plugins-broken/ or similar, using FTP access.
2: If it does, then start enabling plugins one by one until the issue reappears. Then you’ll know what caused it.
After trying all the solutions, finally came to understanding that it was a memory limit issue on the httpd.conf apache server setting. After increasing the limit for RLimitMEM = 204535125 it was working!
this link really helped! incase someone faces this issue in the future please look into the httpd.conf settings for the memory limit. Further reference from a previously asked similar question: PHP out of memory error even though memory_limit not reached
My Problem
I manually installed WordPress on a Debian 9 VM in Virtual Box on a Windows 10 machine. When I pull up the website, this is what I get:
A WordPress site with just HTML, no formatting
The point of this install was to learn how to make a custom WordPress theme. I have built child themes before, but never a theme from scratch, so it may be I don't have everything set up yet. But there is a second issue is WordPress does not give me an option to select my second theme either.
What I did
To set up the site, I followed this tutorial on setting up WP on a Debian system. I sort of touched up on this, but I am new to WP development. I thought this was a quick and dirty route to set up a WP install. I don't have the knowledge of WordPress to know if there is an error in this setup guide.
Again, I checked the themes folder. I could not find the custom theme I started to build as an option. I can't currently download themes straight from WP because I don't have an FTP server/client currently installed on my machine. If it were just the inability to choose a WordPress theme from the WordPress theme repository, I'd suspect it's the FTP setup. But, I also can't choose my custom theme. So is there something wrong with the install?
Summary
I can't get any formatting to work on my WP development site. I suspect it's some problem with themes, but I don't know enough about the internals WordPress to know how to diagnose the problem.
Thank you for your time
It's tough to say without seeing your setup exactly, but this is often caused by URL problems.
Are you able to access wp-admin? If so, try logging in and visiting the settings > permalinks page, then just hitting the save button.
Try reloading your site. It might be fixed.. If not, a little more to try. First, I'd open your browser's Console / Inspect mode, and see if there are any console errors (showing CSS files not loading, etc). If so, post them here.
Additionally, I found a helpful article that details some other things to try when this problem pops up:
http://wphelp24.com/how-to-fix-wordpress/how-to-fix-wordpress-css-not-loading/
I have a fresh wordpress 4.0 install on my server for a specific domain and when I make changes to any of the theme files it won't show up in the browser for a few reloads. I just add "asdf" to the theme file to test changes. I can refresh 20 times but no changes show up until like 20 seconds later.
What I have tried:
Turned off firefox's cache.
Turned off wordpress cache.
Tested other domains on my server with wordpress and they work properly.
Installed wordpress with "server installer apps"(3 times) and also with manual installation.
I refresh with ctrl+f5
Tried with firefox and with chrome, same results.
Its a fresh install so no plugins, no settings changes. There is no caching and my other domains work properly. No errors show up in the console.
I have no idea what the problem could be. My server company, mediatemple, said it could be my ISP, but other domains on my site work properly from the same computer/network. For some reason the problem is specific to this domain and the problem persists through all the themes.
I don't know what to do next. Any suggestions would be greatly appreciated. :)
Update:
Have tried manual install of wordpress 3.9 and that does nothing.
I added a new folder to the root and in that folder I added a file called index.html to test if this file, which is unaffected by wordpress, would show instant changes and IT DOES. So the problem seems to be based within wordpress and specific to this domain.
I spoke to Mediatemple for the 3rd time now and this guy was much more helpful and he actually solved the problem.
When you add a domain to mediatemple it automatically sets the PHP version to "FastCGI", which normally is fine, but it caused problems specifically on this one domain's wordpress install for unknown reasons. So he switched the PHP version to "CGI (Stable)" and that fixed every problem.
I hope this will be helpful to someone in the future. :]
I use joomla 3.1.5, php 5.4.20
When my php was 5.3.x everything was fine but after upgrading php to 5.4.20 i cannot create new article categories!
I get Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
This is not an issue with .htaccess (don't have any) or permissions(checked it a lot of times).
Strange thing is that when i enable debug system in global configuration the problem is solved!!! When disabling debug system problem comes back.
This only happens in joomla 3.x installations. I use the same server with joomla 2.5.x and it works fine.
Any suggestions? thanks in advance
Have you checked the Joomla forum ? PHP 5.4 is not used much and the Joomla 3.1.5 might have some modules that are not compatible with the PHP 5.4.
Just wanted to share the fix to this problem. EAccelerator was causing the issue after disabling it everything works fine
I don't think the main problem is with the PHP version.
To be able to Create New Categories do this :
In your joomla "Control Panel" page, this is usually the first page when you log in, scroll down and under CONFIGURATION click "Global."
In the new page for "Global" that open opens, look for "Default Editor", if you have not changed it before it's value should be "Editor - TinyMCE". Change that to "Editor-None." --Note that for now you will not be able to use the default WYSIWYG.
Click "Save & Close".
Now go back to the page for creating new categories, refresh it and create your categories.
To have access again to the default WYSIWYG, after you have finished creating your categories, go back to "Global " and change the editor back to TinyMCE.
Good Coding.
I have a WordPress theme that's installed and has been running fine for a while. I recently needed to update the theme itself, and I did so use the built-in theme editor. Upon reloading the site, the theme changes are not presented in the markup.
Removing the index.php file from the theme or changing its name results in a blank page as expected, but removing all contents of the theme's index.php does not have a similar effect. In fact, the WordPress installation continues as if I had not made index.php blank.
I have no caching plugins installed, Varnish is not present, memcached is not in use at all, and neither is APC.
I attempted upgrading all the plugins and WordPress itself. The raw-html plugin I have installed failed to update with a fatal error about an include on line 16, but that include was not present. The update worked fine when I renamed the plugin filename though (from raw_html.php to raw_html1.php).
I have found that the cache is the biggest issue when dealing with WordPress; Even when you don't have the cache enabled for the site. I have found that if I make the edit and look at it later, the changes have been updated.
This is not ideal for development.
Sometimes a plugin will have some type of a caching issue (even if the plugin doesn't deal with the cache) that causes the problem.