oMega_2093

Hi there!

Looks like you have some serious Linux setup over there!

Your WordPress is not loading, but what exactly is it doing when you try to access it? Does it throw any error message, or is a HTTP code returned at all? You may be able to find something useful in the error log from the web server.

If the other site you have -which seems to be static- is working, maybe this has something to do with PHP configuration? I am aware that issues can arise if you are using the PHP-FPM, but I’m not sure about other methods. Please double check the PHP config for your site.

I’m curious about your setup, what advantages did your department see when they configured it that way?

Cheers.

Hi there,

I like the Polylang plugin, since it makes maintaining translations a breeze, and allows you to display content on a per language basis. I wouldn’t recomment to configure it as a Multisite install, mostly because you will not be using multiple sites, but a single site with translations instead, that must be handled differently than sites.

This plugin will also allow you to translate your site, and show translated versions to visitors depending on a number of parameters you can configure, so it’s basically the right tool for the job here.

Cheers.

Hi there,

Take a look at your 1st line:

<?php/**

Would you remove that /** and check again? I suspect it might be causing trouble.

Hi there,

Keep an eye on www: if your blog is being served to www.example.com, type that in your hosts file instead of just example.com.

Did that help?

Hi!

You see white screen because your WordPress may be configured to hide errors. To configure WordPress to display errors, you must edit wp-config.php and find the following line:

define('WP_DEBUG', false);

In my file, it’s line 80. Change false to true, save and upload the file. Reload now your homepage and see what happens. You will probably see something else stating what the error is. Paste it here to get further help. It may be your theme, some plugin or any kind of modification, we still don’t know. The message will tell us.

I recommend that before you start any inspection by yourself, you’d better make a copy of your WordPress files and database, just in case, but keeping track of what you change and its original values will be enough to be safe.

You mean something like this? https://imgur.com/a/H7usV

I have managed to create those galleries (and more) which use the core WordPress gallery and some manual shortcode tweaks, like adding type=”carousel” and the like. They also have custom image sizes to help load the lightest possible image.

Those galleries belong to a private theme of mine, but I am slowly releasing its features as public plugins. While all those galleries I post are fully responsive (thanks to Bootstrap), I’m not sure about the best way of making them responsive out of my private theme.

Will think about it!

I’m having the same issue. The pre-commit is guilty for this. Will it be updated? It doesn’t seem reasonable to force the use of a legacy Composer, does it?