HenrikRClausen

Google webmaster tools pointed me to a folder of still-compromised files on the server.. That might be the cause for Firefox to handle the site with caution. Resolving..

Am dipping my toes into SSL, using Let’s Encrypt. That was dead easy to set up on my hosting provider, but it looks like I’m not entirely where I need to be – FF gives a warning about “Mixed content”. I’ll figure out exactly what that means, and how to deal with it.

And the site is still broken in FF on Linux, works elsewhere. Weird, but a lot better than yesterday ??

Could be. It happens in FF only on one of my devices, the site works on my Android tablet.

I’ll assume that going SSL will help a lot, too.

Thanks for the input – while I’m not quite sure what was wrong, at least I’m back on track now ??

My goodness, it works in Chrome!

Still broken in Firefox. I’ll investigate that issue.

Updating with the latest (non-)findings:

The caching we used was WP Total Cache, I found a folder from it. WPTC does have a minify option, which makes it a suspect. So I tried renaming those folders, re-installing the plugin, activating/detactivating it. All to no avail.

Also, I replaced every one of the original WP files through FTP, still no luck.

Essential parts of the theme CSS (every theme) is being disabled somewhere in the loading process. And I’m stumped. It must be discoverable somehow. Could it be hidden in the database rather than in the WP files on the web server?

• This reply was modified 6 years, 5 months ago by HenrikRClausen.

Thanks for the suggestions, guys ??

I had already tried to disable all plugins, and retried it the more brutal way by renaming the ‘plugins’ directory. Nothing here.

Also, i tried switching to other themes. They all behave pretty much the same way – but not entirely. I do get a heading picture with Proximity, so the themes have some effect. Apparently, key elements of the CSS are being negated somewhere. If I figure out where, I can fix this.

Renaming the ‘Proximity’ directory just gives me a ‘directory not found’ message, not a fallback to a WP default theme. At the moment, I’d be happy to have any theme working.

As for caching, we used to have that, but I disabled it a while ago, knowing that ‘stable’ precedes ‘fast’. It makes sense, though, to look for a remnant of caching files that breaks stuff still.

The “Deceptive site ahead” warning would be due to us not having switched to SSL (https://) yet. That’s a task for a later day, when the site as such is working.

I’ll tinker on. My next step is to replace all WP files with FTP, rather than just let WP reinstall itself. There would be some backing up to do, like of the wp-config file.

Still puzzled, still learning…

• This reply was modified 6 years, 5 months ago by HenrikRClausen.
• This reply was modified 6 years, 5 months ago by HenrikRClausen.
• This reply was modified 6 years, 5 months ago by HenrikRClausen.

More radically, I want users to be able to purchase more votes ??