Error message above header

[blueprint]

Hi support team,

I just exportet the .json file from a website I created as base for another one and this Error message appeared above the header. Can you please tell me what to do?

furthermore I can’t find the custom CSS in the Customizer of the new X version anymore. Where can I find it now?

Tahnks!

[rad]

Hi @blueprint,

Thanks for reaching out.

I can see the warning but I’m not sure what’s causing that. Would you mind providing your FTP login credentials as well?

And from what version you upgraded it from? It could be too old and there are feature gaps between that and the latest version.

The CSS should be available in X or Pro > Theme Options > CSS or in the builder, Cornerstone > CSS. It’s the icon CSS in the left panel.

Thanks!

[blueprint]

I found the CSS field, thaks!

The X version of the original site was updated from the previous release. The development site was installed with version 6.

[ruenel]

Hello There,

Thanks for providing the information. We have logged in and regretfully we could not find the correct directory. I would recommend that you find the wp-config file and disable the debug mode. You can do this by opening wp-config.php and adding

define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

When you revisit the page, you should no longer be seeing those warning message.

Please let us know how it goes.

[blueprint]

Thanks. There seems to be a bigger problem: I can not upload images. Whenever I try to upload an image the preview thumbnail is white, the image is not visible. There are no more warnigns from wordpress, so I can’t see what the problem is. I already tried to change the permissions to the wp-content/uploads folder to 755 with no effect. I couldn’t find a solution on google…
Something seems off in general.

[ruenel]

Hello There,

Please double check the ftp details and make sure that we can access the same file directory so that we can investigate further. We need to check the error, the permissions and your wp-config file.

Thank you in advance.

[blueprint]

If you mean you need the path to the directory of the development page it is this:

[christian]

Hey @blueprint,

Your image issue is server related. I tried to upload an image and it is successful but viewing the image directly, I get a forbidden message (see secure note). Please contact your web host for this. This is not caused by the theme.

Also, I still see the warning in your site. It’s just a warning though so and you can disable that by following this guide.

Thanks.

[blueprint]

Thank you. I will disable the warning, but that won’t solve the problem, right? What does ist mean and isn’t it necessary to fix this?

[christian]

Warnings don’t affect the functionality of a site though yes, it must be fixed. I’ve switch to the default WordPress theme and the error is gone but that does not necessarily mean X is causing the issue. It could be a combination of your server and WordPress setup.

I did a quick search about the error and found that it’s mostly related to PHP 7.2

I installed a debug plugin in your site and found that you’re using PHP 7.2 so the issue might be related to that. Please contact your host to downgrade your PHP version to PHP 7.0

Thanks.

[blueprint]

thanks for that info! I’ll try the downgrade.

My web host found out that viewing pictures was not possible because of insufficient permissions of the uploads directory.

Thanks!

[ruenel]

Hey There,

We are just glad that you have figured it the reason why viewing pictures was not possible.
Thanks for letting us know!

Best Regards.

[blueprint]

I downgraded the PHP Version to 7.1 and the message is gone. Do I have to stay with PHP 7.1 for good? Isn’t updating PHP version from time to time improtant for better performance an loadng times? Why is X not compatible with the latest PHP version?

[thai]

Hi There,

Our Pro & X themes are compatible with all PHP versions 5.2 and up (just like WP). We always encourage using PHP supported versions though.

You are seeing a PHP Warning message. This warning came from the core WordPress files. Usually when the variable is unset or null, it returns the warning message.I can also see WordPress team are working on fixing this issue.

Regards!

[blueprint]

All right thanks for that info! So can swich back to the latest PHP version and just wait for an update of WordPress, right?

[christian]

Yes. It’s only a warning so it won’t affect your site.

Thanks.