studiopress / seo-data-transporter Goto Github PK

Rank Math has gained popularity, and some users would like to be able to transfer their SEO metadata from or to the plugin.

Have you done the following in preparation for release?

• Bump version in {plugin-slug}.php, package.json, and readme.txt.
• Test and bump tested up to to the latest WordPress release.
• Run any necessary build routines (npm run build).
• Generate POT (npm run makepot).
• Verify changelog has been updated.

Several requests for Thesis 2.0 support:

https://wordpress.org/support/topic/thesis-to-geneis/
https://wordpress.org/support/topic/thesis-2-x-to-yoast/
https://wordpress.org/support/topic/add-support-for-thesis-2x/

A user requested support for Yoast SEO → SEO by Squirrly: https://wordpress.org/support/topic/seo-by-squirrly-support?replies=1#post-7679462:

Hi, this looks like a great plugin. Would you consider support for exporting from Yoast SEO to SEO by SQUIRRLY? Is there anything I can do to help with this? Thanks.

As reported on WP.org here, attempting to activate version 0.9.10 of the plugin on WP 4.2.2 results in this fatal error:

Fatal error: Call to undefined function seodt_meta_key_convert() in /path/to/site-root/wp-content/plugins/seo-data-transporter/plugin.php on line 186

Modifying the activation hook in plugin.php (line 183) to include the functions.php file seems to resolve this:

Current:

register_activation_hook( __FILE__, 'seodt_activation_hook' );
function seodt_activation_hook() {

    seodt_meta_key_convert( '_yoast_seo_title', 'yoast_wpseo_title', true );
    seodt_meta_key_convert( '_yoast_seo_metadesc', 'yoast_wpseo_metadesc', true );

}

Proposed fix:

register_activation_hook( __FILE__, 'seodt_activation_hook' );
function seodt_activation_hook() {

    require_once( SEODT_PLUGIN_DIR . '/functions.php' );

    seodt_meta_key_convert( '_yoast_seo_title', 'yoast_wpseo_title', true );
    seodt_meta_key_convert( '_yoast_seo_metadesc', 'yoast_wpseo_metadesc', true );

}

It looks like line 133 of functions.php may contain a typo. I think this:

$outout->elements = '';

Should be this, perhaps?

$output->elements = '';

I haven't tested to see what effect this is currently having, but just thought I'd file a report while I spotted it.

Hello Nathan,

Thanks for this great plugin and also thanks for supporting Add-Meta-Tags.

It seems there is a problem with the Add-Meta-Tags field names. SEO-Data-Transporter uses the (very very) old description and keywords fields. The fields that are used by my plugin to store data have changed since a long time ago.

Several users have contacted me about SEO-Data-Transporter not being able to locate any Add-Meta-Tags data. I've even replied to a user on your plugin's support forum at wordpress org providing all the necessary changes in order to be able to locate the data.

I'd be grateful if you incorporated these changes into your plugin in one of the upcoming releases.

For convenience I re-post the required changes here as well. These involve changing lines 86-90 96-99 of plugin.php to the following:

'Add Meta Tags' => array(
    'Custom Doctitle' => '_amt_title',
    'META Description' => '_amt_description',
    'META Keywords' => '_amt_keywords',
),

If a pull request would be more useful, please let me know so as to submit one.

IIRC, I had tried to contact you some times in the past about this issue, but perhaps I must had been doing it wrong :)

Thank you in advance. Please feel free to contact me for more info if needed!

Best Regards,
George

Hi,
I used the plugin today and saw that it is using the old name.

Latest version is giving the following notice:

PHP Notice: Undefined index: platform_new in .../wp-content/plugins/seo-data-transporter/admin.php on line 132

Attempting to convert from Genesis to Yoast SEO, I got a fatal error after clicking Convert:

Fatal error: Call to undefined function do_action_() in /home/dreamwhi/public_html/dev4/wp-content/plugins/seo-data-transporter/includes/class-seo-data-transporter-utility.php on line 129

The themes, plugins, and platforms variables need to be declared global so they are in the global scope when used within a function

global $_seodt_themes, $_seodt_plugins, $_seodt_platforms;