amboutwe
Forum Replies Created
-
When you fill in the Site Representation screen in the first-time configuration, a warning (see below / screenshot) appears if you have not filled out all the information. Choosing to continue without filling out the required data means that some data, like social profiles (sameAs schema), will not be output in the schema.
You’re almost there! Complete all settings in this step so search engines know what your site is about.
It sounds like you suggest adding a second warning in the Social Profiles step when the user bypasses the first warning, restating that the prior warning impacts the social profile schema specifically. As you don’t use GitHub, you can consider this your unofficial request for the additional warnings.
The status was set to Resolved because the following points answer your concern about the missing sameAs schema due to a missing Organization logo.
- To output the social profiles in the schema, please fill out the required ‘Site Representation’ data, including the Organization logo.
- To officially request additional warnings, please open an issue on GitHub explaining why these would be beneficial.
The plugin clears cache during activation or deactivation, and after an update. This ensures the new plugin files, functions, and output are available without waiting for cache to clear.
You are welcome to make changes and tailor the plugin to your needs. Please know that updating the plugin through the WordPress admin will overwrite the changes so you will need to re-apply the changes before you manually update the plugin.
At this time, there are no developer filters available to disable the process. However, we have an open internal issue with our development team requesting a developer filter.
Regarding possible impact of removing part of our code, we can’t give you a solid answer to your question as it depends on other factors. We recommend checking out WordPress Jobs, or WordPress Professional Network for development & consultancy. They’ll be able to check the impact of the change and provide advice specific to your setup.
Yoast SEO uses the WordPress-generated robots.txt file by default but allows you to create a static robots.txt file. I see that your sites have the correct generated WP robots.txt files (example links below). Therefore, your shared robots.txt must be a static file on the server.
To use static robots.txt files on each domain, I found a resolved topic on WPML’s support forum containing a workaround. Changes to the separate robots.txt files should be made using SFTP or a file manager and not through Yoast SEO’s file editor. As WPML handles translations on your site, you may reach out to them for advice on translating these files within their plugin.
To switch to the WordPress-generated robots.txt files, please use SFTP or a file manager and rename the static robots.txt file to robots.old. Cache, if in use, may cause the changes to take a while, so clear your site and browser cache before checking for the changes. You can safely delete the robots.old file once the generated robots.txt files are displayed.
wp_cache_flush_group( 'orphaned_counts' )
This updates incoming link counts (internal links). Features relying on this information may be impacted, like orphaned content post filters and workouts, could be impacted or cause other errors if removed.wp_cache_delete( ‘orphaned_count_’ . $post_type )
I don’t see this in the current version (22.7) and a quick search didn’t find it in the previous version (22.6). It’s also not in the current code here. It could be safer than the first one to comment out since it’s not in the current code. As mentioned above, any features that rely on this could be impacted.The 22.1 changelog doesn’t point to a suspected cause for the behavior. However, one of the changes made between Yoast SEO v22.0 and 22.1 (compare) has contributed, possibly indirectly, to the behavior you’re experiencing.
If you have a staging site, we created 4 early release candidates to slowly build to the final 22.1 release. If you setup the staging site with a working 22.0 and upgrade to 22.1 RC1, does the issue happen immediately? Or does it only occur after upgrading to RC2, RC3, or RC4?Does anything in the commit list stand out as a possible culprit?
Thank you for your patience while we investigated this issue. The Custom Result tab appears with ElasticPress version 4.7.2 but after upgrading to their newest 5.x version removes the tab. This means they changed how these are setup and Yoast considers them a private item that should not be included in our settings. Please reach out to ElasticPress so they can investigate what changed and how you can make these public again.
Forum: Fixing WordPress
In reply to: Cannot install pluginsIn the Site Information, it confirms that the directory is not writeable.
plugins: not writableLooking above in the directory, it appears the plugin install path is different than the content directory.
WP_CONTENT_DIR: /usr/www/users/gruenkmn/deutugal/wp-content
WP_PLUGIN_DIR: /home/deutugal/public_html/wp-content/pluginsPerhaps you checked the plugin directory in the content folder which is not the folder WordPress is trying to write. Is that second path writable? If it’s incorrect, I’d guess something in the
wp-config.phpfile set that path and fixing it would resolve the issue, too.What exactly does turning on caching of yoast sitemaps with the snippet above do? Does it save the dynamically created data in a transient so it doesnt look it up every time?
Using the
wpseo_enable_xml_sitemap_transient_cachingfilter to cache the sitemaps will write the sitemap file’s source code to the database in a transient option. When content changes, the transient is updated.Does it output the dynamically created files as static xml files? Does it use whatever caching plugin you have installed once enabled?
No and no.
We use WP-Rocket which by default does not cache xml files. It says so in their documentation. So even with this setting turned on in yoast it will be ignored by WP-Rocket?
It’s best to confirm with WP Rocket how they handle transient caching. But the sitemap file remains an XML file, so based on what you said, I wouldn’t expect the filter to change the caching behavior.
If you want to see the code and exactly what the sitemap cache does, it’s here.
I created up a new local environment, setup composer to install Yoast SEO with wpackagist, and installed version 20.6. I copied the folder to a safe location and upgraded to 20.7. After comparing the two versions for the files you mentioned, I don’t see anything that changed between the two versions to indicate a development version.
Please answer the following questions and provide any additional details that you might think will help us reproduce the issue.
- What Yoast SEO version did you update from?
- What do you see that indicates it’s a development version?
- Which repository are you using to install/update Yoast SEO?
- What environment type is the site using?
You can check under Admin > Tools > Site Health > Info > WordPress > Environment type
Hi @missdonna. It’s looks like you’re almost there. Click on an individual step (title or description) and you’ll see the step level options, like moving the step up/down and adding images.
For the top description, you’ll need to use an inline image. Inline images can be added by clicking inside the text area where you want the image to appear and clicking the down arrow (more text controls) and select ‘Inline image’.
Hi @andronasis. Although the fields are not part of our plugin, I took a second look to see if I could figure it out.
The prefix in the highlighted field is likely
ytand there are a few other fields that start withyt, including one that isytrssenabled(possibly an RSS plugin?). I see you’ve opened topics for the RSS for Yandex Turbo plugin. Looking at their code, they use many of the fields that start with aytprefix, includingytrssenabled. So, it would seem that the fields most likely belong to that plugin.Hope that helps!
Forum: Fixing WordPress
In reply to: How do I hide the “archive” text?@aksh007 I see that you have Yoast SEO installed. The plugin sets default templates for the title of your content. You can change the default templates under Admin > SEO > Search Appearance.
The courses archive sounds like a custom post type so the ‘Content Type’ tab should have a course section where you can remove ‘Archive’ from the template or change to meet your needs. If not, check the other tabs to find the courses section with the word ‘Archive’ in the template.
Learn more:
https://yoast.com/snippet-variables/
https://yoast.com/help/list-available-snippet-variables-yoast-seo/We are aware of a reported issue with Gutenberg where the meta boxes under the content can be pushed to the sidebar, sometimes accidentally. In short, the under content and sidebar list of boxes appear to be a single list.
Luckily, you can drag and drop the meta boxes between the sidebar and under the content. Additionally, you can use the up/down arrows (image) to move between the sidebar and under content areas. In some cases, you may need to have at least one meta box available to move the boxes between the two areas.
Screenshot: https://pasteboard.co/JpHnJRw.png (see below for more details)
- Make sure you are in the correct sidebar. The gear icon (1) should be selected and you should be in the ‘Document’ (2) section.
- Make sure you move the correct panel. The top ‘Yoast SEO’ (3) panel cannot be moved. Scroll down and look for the second ‘Yoast SEO’ (4) with the up/down arrows.
- If the ‘up’ arrow is gray, enable the ‘Custom fields’ or another meta box. You can do this under the kebab (three dot) menu (5) > Options.
- Be patient. It may take a little trial and error to determine which option works best for you.
Title Formatting:
I spun up a local test environment and installed the same Genesis child theme, the Genesis featured image plugin and Yoast SEO. The title column does not appear squashed on my monitor. I know my monitor is large so I checked the window size and it’s currently at 1400×1084. So I made is smaller width wise and the title column shrinks to a few characters wide when around 1120 wide. I, then, rolled back to the 14.7 version but the screen behaves in the same fashion. Behaving the same in both the current and previous version means updating did not directly impact the issue.This might be different if you have more/less columns than what the default columns with just these plugins and theme. If you have other plugins that add columns, these would take up more space and would cause the smaller title sooner.
This further confirms that it’s due to the limited amount of space available and the number/size of the columns being displayed. Some columns are fixed in size while others are flexible and adjust to the remaining available space.
This is not an uncommon issue as the title seems to be the first column that becomes hard to read. I found a solution (here) that adds custom styling to the title column in the admin area which you might ask your theme developer to incorporate into your setup. Or you can manually do it on your own. Typically code snippets are added to your theme’s functions.php file or you may find a plugin that allows you to add them without editing files. If you’re not familiar with using code snippets, these articles have wonderful advice:
http://www.wpbeginner.com/plugins/how-to-easily-add-custom-code-in-wordpress-without-breaking-your-site/
http://www.wpbeginner.com/beginners-guide/beginners-guide-to-pasting-snippets-from-the-web-into-wordpress/Sidebar Not Showing
Your browser console will show you more information, including JavaScript errors. How to find JavaScript errors with your browser’s console?Some of the errors appear on multiple pages so they likely aren’t causing the sidebar to disappear. However, there is one error that stood out as a likely cause:
Uncaught TypeError: Cannot read property 'page' of undefined
This looks like a page cannot be retrieved. This doesn’t appear on the few other pages on your site where I see the sidebar. Hopefully, your theme author can help pinpoint the exact cause for you.Additionally, when I tested the theme and plugins for the title issue, I noticed that the theme version on your site (1.0.x) didn’t match the version I used (1.3.x). I, also, found that the version I last downloaded had a newer update (1.4.x) which I tested as well above. It’s possible that updating your theme may help with the sidebar and title issue.
WordPress 5.5 Update
If installing it doesn’t fix the issue, I wouldn’t recommend keeping it.Update Yoast on another site
As you might expect, we always recommend updating as soon as possible. But I understand the hesitation when you’ve run into an issue. With what we’ve covered above and given that the other site doesn’t have the Feature Image plugin (which takes up a portion of the available width), I wouldn’t expect the Yoast update to cause any problems on your other site. For the health and safety of your site, we recommend creating regular backups of your site and database. Learn more about the benefits of regular backups. This provides you with a safety net in case something breaks or you want to rollback the update.Title formatting in post overview
I completely understand that something has changed and you need all the columns. I’d just like to confirm that hiding some of those columns fixes the title being squashed. Then we can move to the next thing. Can you confirm that hiding a few of those columns fixes it?Sidebar not showing on page
Sidebars on the frontend of your site are handled by your theme and they would be the best team to help you troubleshoot it further. The Genesis support team can be reached here. I believe StudioPress requires an account to access their support team.Please note that your site is running the current WordPress 5.5 which made a huge change to the jquery (stuff behind that scenes) and some plugins/themes are breaking. You can read more about that in the release master notes here. The downside is that if jquery breaks at any point by anything on your site, it can potentially break everything else. Looking at the browser console of that post, I see quite a lot of errors; mostly around what sound like ads, tracking and cookies.
I, also, checked the plugin ‘Display Featured Image for Genesis‘ and it does not show that it is compatible with WP 5.5. That doesn’t mean it’s breaking anything just that the developer has not confirmed the compatibility yet. I mention this since the plugin also impacts the post overview where you’re seeing the title issue.
As a temporary workaround for those experiencing issues, the WP team provided a helper plugin that re-adds what was removed in relation to jquery. I had an odd issue on one of my sites and the helper plugin is working as a stop-gap measure until I have time to find the root cause or a plugin/theme update comes along that fixes the issue. Perhaps it’ll help your site, too?
- This reply was modified 5 years, 9 months ago by amboutwe.
