Forum Replies Created

Viewing 15 replies - 496 through 510 (of 18,953 total)
  • Moderator threadi

    (@threadi)

    The reason for the warning is an addition that was made with 6.6. The background is explained in the ticket: https://core.trac.ww.wp.xz.cn/ticket/61276

    It also explains how to disable the warning or make it less likely. There is the hook wp_autoloaded_options_limit_size_in_bytes where you have to set the limit value higher.

    Moderator threadi

    (@threadi)

    I would recommend that you report the issue on CoreTrac. In particular, you should include the post ID so that the issue can be reproduced if necessary: https://core.trac.ww.wp.xz.cn/newticket – this is the only way to actually fix the problem.

    Moderator threadi

    (@threadi)

    I recommend getting in touch with WooCommerce’s support about this via https://woocommerce.com/my-account/create-a-ticket/ if you have any of their paid WooCommerce products or https://ww.wp.xz.cn/support/plugin/woocommerce/ if you do not.

    Plugin Author threadi

    (@threadi)

    Unfortunately, no, not yet. The reason is that WordPress itself does not (yet) support subdirectories. Importing files from such structures could cause issues, as the directory structure cannot be preserved. To make it worse, there might be files with identical filenames in those directories – you cannot store duplicate files in the media library, and you wouldn’t be able to tell them apart.

    I have an issue regarding this for ZIP files, but it certainly applies to any external source. One idea for these directory structures is to use one of the many directory plugins. Then you could map them using that.

    If you’re already interested in this, what would you expect these directory structures to look like in the Media Library? Then I could take that into account for further development.

    Plugin Author threadi

    (@threadi)

    That sounds like a PHP syntax error to me. Take a close look at what you copied and what you pasted. There’s probably a character missing somewhere in your file.

    Moderator threadi

    (@threadi)

    The terminology here is very important. The Embed block actually uses the oEmbed format. This is an open format for embedding content from Website A into Website B. Both websites must support this format.

    However, this is different from embedding a website using an iframe. No special format is required for this that both websites must support.

    So if you simply want to embed a website into yours, an iframe would be more suitable than the oEmbed format, since the latter is less widely supported.

    Note, however: both formats require that neither of the involved websites prevents them from being embedded via an iframe. This is also a security setting that many website operators use nowadays. They want to prevent their content from appearing on websites they cannot control. Every page view costs traffic, and if you give that away for free, you potentially lose real visitors and – especially for online stores – revenue as well.

    Moderator threadi

    (@threadi)

    I recommend getting in touch with Elementors’s support about this via https://elementor.com/support/ since you have Elementor Pro. We can’t provide assistance with commercial products here on the forum.

    Moderator threadi

    (@threadi)

    The cleanest solution would be to create a custom template for this page that doesn’t include the header. Unfortunately, since you’re using “Unos Premium,” a commercial theme, we can’t help you with it here in the forum. This leaves you with the following options:

    • Contact the theme’s support team, which you can likely find here: https://wphoot.com/support/
    • Or try the following custom CSS: body.page-id-3631 #header { display: none; } – you’ll likely need to add this under Appearance > Customizer > Additional CSS if you’re using a classic theme. Note that the page ID in the CSS code must be unique. I’ve taken this from the page you linked to. If you want to use a different one, you’ll need to update the ID accordingly.
    Moderator threadi

    (@threadi)

    If there are multiple words, WordPress’s built-in search looks for all of them. “About” is found because all three terms appear in the content of the “About” page. You can check this yourself by searching for each of the three words individually in your browser while on the page.

    Moderator threadi

    (@threadi)

    No, this uses WordPress’s built-in search function, which can also be used on the front end. By default, it searches in titles and content. This can also be customized using the hook mentioned above. I suspect there are plugins for this as well, but I think they tend to work on the front end rather than the back end.

    Moderator threadi

    (@threadi)

    This heading is generated by the theme you’re using in the page header, where it’s used as the page title. This is, of course, incorrect and should be fixed.

    However, you’re facing the challenge that you’re using “Resort” by WooThemes, an extremely outdated commercial theme. According to my research, the last version released was 1.1.10 in 2017. You’re using 1.0.5, so your theme is likely 10 years old. In addition to SEO-related issues like this, you’re exposing yourself to other risks that could potentially jeopardize your website – in terms of design, reliability, and possibly security as well.

    Please note that we cannot provide assistance with commercial products here in the forum. Normally, you would need to contact the theme’s support team for a solution, but in this case, that is no longer possible.

    You therefore have the following options:

    Moderator threadi

    (@threadi)

    The issue here is with the preview in the Block Editor. When using the embed block, the URL to be embedded is loaded via an iframe. This is visible to you in the Block Editor because the editor runs a script that removes the actual style rules intended to hide it. As a result, you see the mobile view of the external page in the Block Editor.

    This isn’t visible on the front end because WordPress correctly embeds the iframe in the HTML code but doesn’t remove the style specifications that hide it. In fact, you won’t be able to embed this page this way.

    I also tested this with the Gutenberg plugin. There, no preview is generated in the editor anymore. It looks like this:

    https://snipboard.io/hfZ5vT.jpg

    I therefore suspect that what you’re seeing in the current WordPress 6.9.4 is still the case, but will be optimized in the next version, 7.0.

    Moderator threadi

    (@threadi)

    Your screenshot confirms my suspicion. The term appears in too many records – more than 50, in any case. The fact that the specific page you’re looking for, with that exact name, doesn’t show up is more of a coincidence.

    This search performs a database query similar to the search field on the site overview. It searches the titles and content of published content types. Here is the code for it:

    https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/ajax-actions.php#L2247

    If you were to use a more specific term, such as “Hospital” or “Memorial” you would likely find the portfolio with those terms in its name.

    So I don’t think the search with this term doesn’t work at all. I think rather that the search results don’t meet your expectations. I see two options for you:

    • You could try to influence the database query that triggers the search. You can do this, for example, with the PHP hook pre_get_posts.
    • Or you can open a ticket in Core Trac so that Core developers can further optimize it if necessary. It’s best to describe what the search should return according to your expectations: https://core.trac.ww.wp.xz.cn/newticket
    Moderator threadi

    (@threadi)

    I can’t reproduce that at all. I have a project here with over 100 posts and two dozen pages, one of which is also called “About”. When I search for it in the location you described, I find it and can use it.

    What does the output show when you can’t find the page? Does it say “does not exist” or are other results displayed? Regarding the latter, please note that for performance reasons, the search is limited to a maximum of 50 results per page. You may have multiple results, but you just can’t see that exact page because of this.

    Another tip: try using a different browser. Browser add-ons can also negatively affect such interactions.

    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.

    You can also try deleting the plugin via FTP. Your hosting provider’s support team can help you with this as well.

Viewing 15 replies - 496 through 510 (of 18,953 total)