JS Morisset
Forum Replies Created
-
Forum: Plugins
In reply to: [JSM Inherit Parent Featured Image] PHP Warning in featured imageThanks for reporting the issue – the latest version should fix that. 🙂
js.
Forum: Plugins
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Plugin won’t update.The WPSSO Update Manager provides Premium updates for the WPSSO Core Premium edition. This is a support forum for the WPSSO Core Standard edition. If you’ve purchased the Premium edition, you can open a ticket here: https://surniaulula.com/support/
js.
You probably meant to post your question in the WPSSO MRP support forum at https://ww.wp.xz.cn/support/plugin/wpsso-merchant-return-policy/, but I can answer your question here as well.
After activating the WPSSO MRP add-on, you can create one or more return policies under the SSO Returns menu item in the left-hand side WordPress admin menu. You can choose for that return policy to be the default when creating/editing a return policy, or create several return policies and select them in the Document SSO metabox when editing products.
js.
Forum: Reviews
In reply to: [WPSSO Core - Complete Schema Markup and Meta Tags] Great pluginThank you! 🙂
js.
We had a DNS DOS attack which caused an interruption to our services – sorry about that. Normally that IPv4 consistency check is a good thing, but if our DNS servers are offline, that would create a problem. I’ll have a look at creating some fallback logic in the plugin, just in case a situation like this ever happens again. Thanks for reporting the issue.
js.
I’m guessing that you mean links in the metabox tabs? And the metaboxes are blank, aside from the tabs? That would indicate a javascript error caused by your theme or another plugin. A javascript error will cause the web browser to stop executing all javascript after that error, which would prevent WPSSO’s own javascript from executing and displaying the metabox content.
See here for info on how to view the javascript console and get the error message:
You should report the error to the related plugin or theme author.
js.
@fraughtithrouble Retrieving video details from video hosting services (Facebook, YouTube, Wistia, Vimeo, etc.) is provided by the Premium video modules in the WPSSO Core Premium edition, so this reply will not be useful to readers of this forum (a forum dedicated to supporting the WPSSO Core Standard edition). If you have further questions about Premium features, you can open a Premium support ticket at https://surniaulula.com/support/.
To include/exclude/modify video image preview URLs, you can hook the ‘wpsso_og_video_image_url’ filter and return false, an empty string, or an image URL (the default one or a different one). See https://wpsso.com/docs/plugins/wpsso/notes/developer/filters/ for a complete list of available filters.
js.
When WPSSO is active, it provides CSS for column widths when listing posts/pages/products. When WPSSO is not active, it is not providing any CSS, so formatting would be the default provided by WordPress, WooCommerce, etc. The only reason why old CSS might still be in your webpage is if you have a caching plugin that did not refresh itself properly (you should report the issue to its authors), or your HTTP caching headers are incorrect for dynamic (ie. logged-in user) content. If you use a caching plugin or service, try clearing it’s cache, and if you don’t, then try a forcing reload in your browser (ie. shift-reload) and report the incorrect HTTP caching header values to your hosting provider.
WPSSO provides meta tags and Schema markup in front-end webpages. You should not have duplicate meta tags or Schema markup from other plugins in your webpages as that will confuse Google and other crawlers. WPSSO suggests disabling the duplicate meta tags and Schema markup form Rank Math as WPSSO generates better meta tags and Schema markup.
js.
It sounds like WPSSO may be triggering a bug in another plugin. I would suggest activating the Query Monitor plugin, defining the WP_DEBUG constant, and checking for related errors. See here for more info: https://wpsso.com/docs/plugins/wpsso/installation/troubleshooting-guide/
js.
If the Add Text Property option is unchecked, then the ‘text’ property (https://schema.org/text) will not be added to the Schema markup.
I’ve updated the Full Text option help in the next version from:
The complete textual and searchable content for this creative work.
To:
The complete textual and searchable content for this creative work. The default value is the post content with shortcodes and blocks expanded and HTML removed. You may hook the ‘wpsso_the_text’ filter to modify the default value.
js.
If WPSSO is reporting serious issues with your site, you should fix your site. There is nothing to fix in WPSSO, it is reporting issues when issues are detected, and you have a choice to fix those issues or not. If you prefer not to fix serious issues, that affect the quality of the Schema markup and meta tags that WPSSO creates, then you’re probably better off with a different plugin – one that will work with a site that has serious issues. Either way, you probably won’t get good Schema markup and meta tags from any plugin without fixing those issues.
js.
WPSSO will report an issue only if there is an issue – on most sites there are no issues to report, so no notices. Warning notices can be dismissed (they are contextual to the current editing page), but serious error notices cannot be dismissed – to “dismiss” an error message, the error needs to be fixed. For example, if you’ve published a post (not just saving a draft) without selecting an image (featured, custom, etc.), then WPSSO will show an error notice about the missing image so the error can be fixed at that moment (before Google crawls the published page and shows an error in the search console). WPSSO does not show any warning or error messages usually, and if it does, it’s often just an overlooked WordPress or WooCommerce setting.
What you’ve described is trying to use WPSSO on an old site that was not setup properly and you’re finding that WPSSO is reporting too many warnings and errors. As I’ve said, you have choices – you can deactivate WPSSO, fix the site and reactivate WPSSO (as WPSSO can’t create complete and accurate Schema markup and meta tags anyway, so there’s no use running it), or you can deactivate WPSSO, leave the site as-is and choose a different plugin. Considering the errors that WPSSO is reporting though, no matter the plugin, you probably won’t get very good Schema markup and meta tags from those other plugins either (they likely won’t report any issues though, which sounds like it may be preferable to you).
js.
If you’ve activated WPSSO on an old site that doesn’t use WordPress image size names (for example, where small image thumbnails were uploaded instead of full size images), you can expect at least two error notices when editing a post (for example, a missing Schema markup and Open Graph meta tag image) as WPSSO looks for proper images (see https://wpsso.com/docs/plugins/wpsso/faqs/how-does-wpsso-find-detect-select-images/) and doesn’t find any. WPSSO is a WordPress plugin that was designed around WordPress features, like properly coded themes that use image size names. Using the WordPress Media Library correctly also means that your theme can provide images for high resolution displays, responsive layouts for varying display sizes/shapes, and image sizes that Google, Facebook, etc. require. On a properly designed site, you wouldn’t see any notices from WPSSO unless you’d forgotten to add an image when publishing a post or forgotten some other basic WordPress or WooCommerce configuration settings – the checks that WPSSO performs are designed for this – as a reminder. If you’ve activated WPSSO on an old site that you know isn’t designed, coded, or been managed properly, WPSSO is likely to show a lot of error messages. The issue isn’t the WPSSO plugin, the issue is the site. You can deactivate WPSSO, fix the site and reactivate WPSSO, or ignore the site issues and use a different Schema and meta tag plugin that doesn’t rely on WordPress and WooCommerce being configured and used properly – there’s lots of choices for those.
js.
It sounds like you are working on an old site with content that does not meet social and search site requirements (ie small or missing images, pages, etc.), while at the same time using a plugin like WPSSO that attempts to create complete and accurate meta tags and Schema markup for social and search sites.
I’m not sure if you see the inherent conflict there – you would either need to update your content, or use a plugin that isn’t so focused on the quality of the Schema markup and meta tags it produces.
js.
WPSSO may report Schema markup and/or meta tag errors when editing or updating a published post. Generally there are no issues to report and no notices.
WPSSO can create update, informational, warning, and/or error notices – although only errors are shown automatically in the current version. An error message is typically about an issue that will affect search results or social engagement negatively. We do assume that this is important to our users.
I understand that some users have old sites with small images – unfortunately small images often cannot meet the minimum requirement of search engines and social sites. For example, a 600px container (which most people would consider a small size) on a website needs a 1200px image to display properly on high resolution displays. High resolution displays and responsive images have been around for many years now, but some old sites may not have been created using WordPress image size features as they should have (ie. a full size image is uploaded and themes/plugins request image sizes by name, which WordPress then creates as needed). In some cases 600px images have been uploaded to be displayed in 600px containers. That is unfortunate as the minimum size to meet all search and social requirements is 1200x1200px. If there are no images found attached, featured, or in a post, for example, WPSSO will show an error message as an image is required (and Google even prefers 3 different aspect ratios of each image). WPSSO does suggest a few ways to fix this, and even offers image upscaling, although upscaling can only be done up to a certain point. 🙂 We have a FAQ that outlines the reasons why uploading small image is not a good idea. https://wpsso.com/docs/plugins/wpsso/faqs/why-shouldnt-i-upload-small-images-to-the-media-library/
You mention the lack of a WooCommerce checkout page, which yes, WPSSO would report if a checkout page was missing and/or incorrect in the WooCommerce settings (ie. a checkout page ID that does not exist), as the WooCommerce checkout page requires specific Schema markup (the account, cart, checkout, and shop pages all require specific markup) and WPSSO must know which post ID is the checkout page. An issue has never been reported with this check, either in the WPSSO support forum or in the Premium support site, so I’m afraid that we cannot be aware of an edge case like you describe if it’s never reported.
js.