we have a multisite network with five subsites and the layout is broken across each of them on our development environment. This even appears to be the case when the theme is changed to the default WordPress twentyseventeen theme, and we have also tried deactivating/activating plugins.
For example on one of the subsites, the layout is displaying like this this:
However it should look like this:
We are seeing a similar issue with the WP Admin interface, again affecting only our development multisite network (not our UAT/production environments).
We are also seeing minor layour issues with options pages in wp-admin:
Although it should look like this:
Changing the theme does not resolve this either.
I can confirm the following has been attempted with no resolution:
Changing to default 'twentyseventeen' theme
Deactivating all plugins
Reactivating the plugins 1-by-1
Checking the theme licensing is up to date
Ensured custom CSS in our development environment matches that in our production environment
Are there any issues that are known to cause this and any known fixes that we may have missed?
Any help will be greatly appreciated.
Related
I'm building a Wordpress theme and one of the things I noticed is that the browser requests a page /none (example.com/none). I see this in the Network part of the inspector:
(This is Chrome). As you can see, the browser spends 676 ms loading it and during that time it almost doesn't do/load anything else.
In a theme check (with a WP plugin) I also encountered the absence of /none as an error.
Is this usual browser behaviour for every website or is this pure Wordpress?
And what should I do to fix it (be it WP or browser behaviour)?
Thanks a lot in advance!
This should be related to your theme files. You can have a look at the wordpress template hierarchy to find out all parts of your theme. https://developer.wordpress.org/themes/basics/template-hierarchy/
Deactivate your theme and use a standard theme. Deactivate all plugins. This way you can make sure that it has nothing to do with your wordpress installation or plugins, but is an issue caused by your theme.
The inspector of your browser might give you the right hints where you can start your search.
I'm trying to help move a website, and I copied a clean version of the twentyfourteen themes from spot A into spot B, but it did not take effect.
Our site (as mentioned earlier) had been injected, so we're relocating our site with a fresh install. On the original WordPress site export did not work properly for the pages, so I do not think it would work for a theme.
Does anyone had any tricks they'd like to share?
Thank you!
The original theme seems to be stuck as the active theme in your database. Do you have any plugins running yet? ...More specifically a plugin that can cache your site?
If there aren't any plugins running, it's probably stuck in your server's cache and needs a bit of time to roll over.
I am a freelance developer, and I normally build sites from scratch without using any code generating sites like WordPress or Square Space. But my current client insists on using WordPress. However, I am rescuing this project from a previous developer who made a big mess because from the looks of it does not seem like they knew what they were doing.
Is there a way for me to restart everything, on a clean slate and template on WordPress? I would like to have none of what the previous developer has done. Also is there a way for me do do direct coding using HTML, CSS, JavaScript etc on a WordPress site?
Yes, you just need to look into how to create a theme, since themes are the basis of the Wordpress structure. Ultimately, if you have the code for a website, it can be broken into separate files that Wordpress can use.
See: http://www.wpexplorer.com/create-wordpress-theme-html-1/
If the previous developer has done all the work in the theme files, then simply switching the theme to a default theme (Like Twenty Sixteen) will give you a nice clean slate to dig in and jump off with. You will want to create a child theme of any existing theme if you want to make any changes. If, however, the developer has messed with other files besides the theme folder, then you will most likely want to export the content only (as a logged-in administrator, go to Tools > Export (here's a screenshot))
Then on a new environment (I prefer testing these things first on a local virtual environment like VVV, and then transition to a development subdomain on the same server that the site will eventually go live on and securing it with an htaccess user/password to block curious eyes), import the content on a fresh installation of wordpress via the same menu (Tools > Import). This will give you a fresh installation with the content that's been created, but without any of the mess.
For more information about importing content - here's the codex article.
I hope that's a good start - but if I've glossed over anything you don't understand, let me know - I'm happy to help.
I have a custom theme (http://aspenwebsites.com/echo/) that works fine on a server here in US.
Today I attempted installing that theme to a server in Kazakhstan and got a White Screen - http://domstroy.kz/
Unfortunately I won't be able to access their database in order to change a selected theme or to their restore options for next 6-8 hours. I'm hoping to find the solution in the meantime while I only FTP access.
My custom theme was built as a modification to WP's Twenty-thirteen. I noticed their WP did not have Twenty-Thirteen WP theme present in the list of themes. So I was hoping by bringing Twenty-Thirteen theme files over via FTP I might rescue the situation. It didn't seem to make any difference.
What else might it be or should I look for or try, since the very same theme works fine on a server here in US.
Remove your theme from the theme folder using ftp. This should force WordPress to choose another one.
Are you running an up-to-date version of WordPress? If TwentyThirteen is missing, was it deleted or is the version of WordPress so old that it does not support TwentyThirteen? If the latter then your child theme won't work until you update WordPress and then put TwentyThirteen on, and then your theme.
HTH,
=C=
I was recently hired by a new company and one of my duties is upkeep on old sites. It's recently been brought to my attention that one of Wordpresses is broken in IE9.
www.nexoslatinos.com
I've tried deactivating all plugins, no fix.
I've tried switching to default themes, even they appear broken.
I've opened the developer tools in IE9 and it's rendering the site in what it calls "Quirks Mode"??
The theme is for the most part identical to the theme found in the spanish translation version:
www.nexoslatinos.com/espanol
which is rendering fine in IE9. When taking the Spanish translation theme and applying it to the first wordpress, it breaks. The two themes also run identical plugins. They are however, different wordpress installations.
When I view the source for the page, I am getting a strange line of code before the doctype:
<!--331c6883dd6010864b7ead130be77cd5-->
Could this be throwing off IE9? I haven't been able to locate the code's origin, but it stuck out when reviewing the site in my initial troubleshooting.
The code for the theme is a bit of a mess and isn't valid, but despite that is displaying fine in Chrome, FF, and Safari.
Thoughts? Insights?
That comment (not code) is an MD5 hash of "pizda" -- which is a eastern european pejorative meaning vagina in various languages. You can see this http://en.wiktionary.org/wiki/pizda for ethnological details.
Check your WP theme for code fragments that might look suspicious. If it's not there, check apache configuration for a site-wide server-side include (SSI).
Don't mean to alarm you as I didn't look at the site, but I would check files, database for malware, whether server-side, client side, or both. Not 100% sure, but additionally there is a pizda kernel exploit - you may want to have the hosting machines checked.
This sounds to me like it could be a file encoding issue. I would recommend checking to make sure all of the php files that make up the theme as well as all Wordpress core files that might have been modified are UTF-8. You can do that in your code editor, or by checking each file here: http://people.w3.org/rishida/utils/bomtester/
A quicker way to narrow down the scope of potentially problematic files might be to create a clean dummy Wordpress installation and activate the seemingly problematic theme. If the problem is still there, it's got to be a problem with one of your theme files. If it's not there, I suspect that there might have been some unsound edits made to the Wordpress core files.