Forum Replies Created

Viewing 15 replies - 121 through 135 (of 18,918 total)
  • Moderator threadi

    (@threadi)

    This could also be a (rare) hosting issue if a server-side cache is being used. As far as I can tell, you’re with GoDaddy. I’d recommend contacting their support team.

    Forum: Fixing WordPress
    In reply to: Krytyczny błąd
    Moderator threadi

    (@threadi)

    The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

    Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

    In both cases you should be able to see what the cause is in the logfile.

    Moderator threadi

    (@threadi)

    This forum is designed to help users like you and me support one another. See also: https://ww.wp.xz.cn/support/guidelines/

    No one here is “my” developer. WordPress is developed by the community, including through feedback like yours, which should, however, be as well-founded and clear as possible. Based on the list of plugins you mentioned and the continued lack of feedback regarding a sample image, I suspect that your problem is caused by one of these plugins and not by the WordPress core itself. As described above, there are already two tickets with the WordPress community developers addressing the recommendations you raised. You’re welcome to participate in this community process in this tickets to help find a solution or wait until someone resolves the recommendations you’ve raised.

    Moderator threadi

    (@threadi)

    If you view your observation as a recommendation for optimizing the WordPress Core, I would suggest opening a ticket for it in Core Trac.

    However, I took a look at the specific lines you mentioned and noticed that you do not appear to be running the latest version of WordPress. For instance, in the current version, line 1469 of wp-includes/media.php contains no PHP code that would trigger the warning message you described: https://github.com/WordPress/WordPress/blob/master/wp-includes/media.php#L1469

    It is possible that this specific issue was resolved in WordPress 7.0 thanks to a ticket in Core Trac; see: https://core.trac.ww.wp.xz.cn/ticket/60480

    Consequently, the other error messages you encountered may also be obsolete. However, there is currently an open bug ticket regarding this issue for height and width specifically in relation to SVG graphics: https://core.trac.ww.wp.xz.cn/ticket/57239

    My recommendation, therefore, is as follows:

    • Update your WordPress installation to version 7.0 and check whether the warning messages persist.
    • If they do, deactivate all plugins to rule them out as the cause. You should also switch to a default theme, such as Twenty Twenty-Five. Users are strongly advised to take this step to ensure that the problem is not caused by a plugin.
    • If the issue continues to occur – even with no plugins active, using a default theme, and running the latest WordPress 7.0 – please feel free to open a ticket in the WordPress Core Trac. When doing so, please describe the exact steps required to reproduce the error (including, if possible, the specific image file that triggered the issue for you): https://core.trac.ww.wp.xz.cn/newticket – only under these conditions will developers have the opportunity to identify and implement potential improvements to the Core.
    Moderator threadi

    (@threadi)

    Have you tried switching to a different theme just to test it out? As you suggested above, it could also be an incompatibility issue between that theme and WordPress 7.0.

    At the same time, I’d recommend taking another look at the error log. You’d be able to see the cause right away there.

    Moderator threadi

    (@threadi)

    Thanks for the details. I took a look at it on my end and can’t find any problem with the shortcode in the editor.

    I tested this in a fresh WordPress 7.0 installation, using only the plugin you mentioned and the HTML block you mentioned along with its content. The exact same process works without any issues in the Playground as well (except that the Playground won’t load the images on the front end, but that’s likely a Playground-specific issue).

    I would therefore recommend first checking whether any other plugins might be interfering here. Try deactivating all of them except for the Gallery plugin whose shortcode you’re using.

    Another tip would be: you’re getting a message saying the code is incorrect. Take a look at the surrounding code in the editor – the error might actually be caused by something completely different. To test this, you could simply create a new page and enter only the shortcode there, with nothing else.

    And there’s one more thing I’d recommend. You’re using a shortcode. So I’d also suggest inserting it via the Shortcode block rather than the HTML block. See: https://ww.wp.xz.cn/documentation/article/shortcode-block/

    Moderator threadi

    (@threadi)

    I just tried to reproduce what you described. Unfortunately, it didn’t work. For me, both HTML code and shortcodes continue to appear, no matter how many times I edit a page that contains them.

    Could you please describe it in more detail, specifically which HTML code or shortcode you’re using?

    I’d also recommend deactivating all plugins to rule them out as the cause.

    Moderator threadi

    (@threadi)

    This is usually a secondary error caused by a plugin you’re using incorrectly calling WordPress core functions. To rule this out as the cause, try deactivating all plugins. If the error message no longer appears, reactivate the plugins one by one until you find the one causing the problem.

    Moderator threadi

    (@threadi)

    If the debug mode isn’t producing any output either, a much more serious error is occurring before WordPress even loads. In that case, I’d recommend taking a look at the server-side error log. There should be something in there.

    Moderator threadi

    (@threadi)

    Yes, it’s likely a server-side error. It might be because a plugin you’re using isn’t compatible with changes in WordPress 7.0. I’d therefore recommend taking another look at the error log to find the cause and, ultimately, a solution.

    Alternatively, you can try deactivating all plugins and change the theme to a default theme like TwentyTwentyFive and see if that changes the behavior.

    Moderator threadi

    (@threadi)

    As I said, that shouldn’t actually be happening. Shortcodes have always been displayed as such in the editor and not interpreted.

    However, this change you’re seeing might be related to some setting in your project. Do you perhaps have any plugins that might have altered this for you? Take a look at exactly which plugins you’re using. Your TwentyTwentyOne theme can’t be the cause.

    Moderator threadi

    (@threadi)

    Unfortunately, I can’t seem to reproduce the issue you described at all. My guess is that a plugin you’re using is causing the problem. Try deactivating all plugins to see if that makes a difference.

    By the way, I also see a known bug on your end (probably the lesser problem for you right now). The links next to the update button are misaligned. You can find the ticket for this here: https://core.trac.ww.wp.xz.cn/ticket/65286

    Moderator threadi

    (@threadi)

    ElementsKit Pro is a commercial plugin, so unfortunately we can’t help you with it here in the forum. Please contact their support team: https://wpmet.com/support-ticket-form/

    Moderator threadi

    (@threadi)

    The theme Underscore is neither being developed further nor supported anywhere. See its repository: https://github.com/automattic/_s

    It’s therefore quite difficult to understand your question. You can’t just download the theme and see your customizations there. We might be able to help if you provide a link to your website so we can see what the issue is directly in the browser.

    Moderator threadi

    (@threadi)

    Your screenshot shows the Block Editor, not the Classic Editor. And I see that so-called shortcodes are visible there – those lines that start with

    [caption]

    These shortcodes are only interpreted on the front end of the website (the public view). And that’s completely normal. Of course, you see them in the editor because that’s where you have to enter them.

    My recommendation would be that if you use shortcodes in the Block Editor, you should place them in the Shortcode block. That also makes the whole thing a bit more readable. See: https://ww.wp.xz.cn/documentation/article/shortcode-block/

Viewing 15 replies - 121 through 135 (of 18,918 total)