Dani

Hello fox-didl,

thank you for your feedback.

I’ve already planned an update that will introduce an option in the settings to control how many alternate version fields are displayed. This will allow you to limit the output to only the alternate version you actually need.

The update is expected to be released by the end of this week or the beginning of next week.

Hello fox-didl,

Thank you for your feedback.

I’ve created a ticket to consider adding this feature in an upcoming plugin update. You can expect a plugin update around February, which may include this enhancement.

To make sure we’re addressing the right use case, could you please confirm that what you need is a widget for the block editor sidebar and also meta boxes (for the Classic Editor) to add hreflang links directly within the post/page/cpt editing screen?

Hello area9,

Thank you for taking the time to leave a review.

I’d like to clarify that the plugin’s description and documentation explain the export feature exactly as it works. The export functionality is intended to generate Markdown files from Markdown documents stored within the plugin, and this behavior is explicitly documented.

For reference, the Export section states:

Export

With this menu, you can generate Markdown files from the Markdown documents stored in the plugin.

This matches what is described in your review. There is no claim that the plugin converts non-Markdown content into Markdown during export.

May I ask where the “not entirely accurate” feature description can be found? If there is a specific sentence or section in the plugin description that you believe is misleading, I would be glad to review and address it.

Otherwise, the review appears to restate the documented behavior while presenting it as an inaccuracy, without pointing to any incorrect description or unmet claim.

Thank you for your time.

• This reply was modified 3 months, 2 weeks ago by Dani.

I wanted to provide an update regarding the previously reported vulnerability. The report has now been removed from the Wordfence vulnerability database.

After reviewing the issue, it became clear that it was not actually a vulnerability. The report, originally from Patchstack, flagged the ability for users with the contributor role to add a standard hyperlink to a draft post as a vulnerability. This behavior is expected and consistent with how the WordPress editor functions.

We contacted Patchstack to clarify the situation, and the CVE ID associated with this report has been removed. As a result, Wordfence, which used Patchstack as a source, has also updated their database and removed the vulnerability.

• Patchstack database: https://patchstack.com/database
• Wordfence vulnerability database: https://www.wordfence.com/threat-intel/vulnerabilities

Hello nyakuza,

Thank you for the detailed feedback.

I completely understand your concerns and agree that the current behavior could be improved. I’ve created a ticket to review and enhance these aspects (default date range, ability to input the dates, possible buttons/pills to disable the date filter) in a future update of the plugin.

At the moment, I can’t provide an exact release date or guarantee which of the suggested improvements will be included, but an update is planned for December.

Hello Rik0399,

Thank you for your kind words. If you enjoy using the plugin, please consider leaving a rating in the Reviews section here on wordpress.org, it helps improve the plugin’s visibility and reach.

Regarding your question:

• You can control the alignment of the form elements via the Options → Content → Alignment option.
• For additional design adjustments, check out Options → Style, where each form element offers its own customization settings.

If you were referring to editing the form content directly as HTML, this feature isn’t currently available. However, I’ve created a ticket for it so it can be considered in a future update.

Hello vsswebmaster,

We have replied to the email address you registered on our site. Please note that questions regarding commercial plugins should be directed through our official support channels rather than the WordPress.org forums:

https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

Thank you for your understanding.

Hello ehsanfotoo,

Thank you for providing all the details.

From your screenshot, it appears that your site is using a separate plugin called Hreflang Flags. This plugin supports shortcodes, and you can find its documentation in the /doc/ folder included with Hreflang Flags.

Please note that we’re only able to provide support for Hreflang Manager in this forum. For any issues related to other plugins, such as Hreflang Flags, we recommend reaching out with the methods described on our support page.

Ref: https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

• This reply was modified 6 months, 3 weeks ago by Dani.