• Resolved jlechevanton

    (@jlechevanton)


    Hi,
    Shortcodes replacement works like a charm but the permalinks of pages are completly messed up (wrong permalinks, wrong titles sometimes, …)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jose

    (@giuse)

    Hi @jlechevanton

    the plugin does nothing else than convert the content of the exported posts to pure HTML after converting all the shortcodes to the output of those shortcodes.

    This means that if you export the posts from https.//your-website-source.com, if inside the content you have internal links, then you will still have the URLs with https.//your-website-source.com after you import the same posts to https://your-website-destination.com.

    You can solve this problem with a search and replace plugin like Better Search Replace.
    Be careful, use it only for the table wp_posts and wp_postmeta, in another case you may have problems with your site. And always after making a full backup.

    Thread Starter jlechevanton

    (@jlechevanton)

    Fully agree, there is no reason for any other content to be modified but…

    My standard export with short code replacement deactivated:

    <title><![CDATA[Home]]></title>
    <link>https://xxxxx/home/</link>
    <pubDate>Mon, 26 Dec 2016 15:01:04 +0000</pubDate>

    The same page with the shortcode replacement activated:

    <title><![CDATA[Home]]></title>
    <link>https://xxxxx/steel-structures-for-waste-incinerator-plant-in-brno/</link>
    <pubDate>Mon, 17 Jul 2017 07:00:09 +0000</pubDate>
    Plugin Author Jose

    (@giuse)

    Hi @jlechevanton

    this is theoretically not possible. Nothing in the code of this plugin can do that. The code of the plugin is very simple. I have checked it again, and I can ensure this is impossible.

    The plugin doesn’t touch what you have inside <link> and </link>

    However, it may trigger an issue with a third plugin. For me, it’s hard to imagine what kind of conflict, but let’s investigate it.

    I suggest you the following steps:

    – Update the plugin to the last version 0.0.3
    – Enable the debug in wp-config.php by adding these lines of code before the content /* That’s all, stop editing! Happy publishing. */:

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    – Install this little plugin that I’ve just created for the debugging: https://plugins.svn.www.ads-software.com/export-without-shortcodes/branches/debugging-exporting.zip
    – Disable Export Without Shortcodes
    – Export the posts
    – Copy the content of wp-content/debug.log
    – Enable Export Without Shortcodes
    – Export the posts
    – Copy the content of wp-content/debug.log and compare it with the log that was written without Export Without Shortcodes

    In the debug.log file, you will find the titles that will be written to the exported file.
    If you find different titles, follow the following steps:

    – Install Freesoul Deactivate Plugins
    – Go to Freesoul Deactivate Plugins => Plugins Manager => Custom URLs => Backend URLs (important! Backend URLs, NOT Frontend URLs)
    – Add a row with this match: *download=true*
    – Disable all the plugins, but Export Without Shortcodes and Debugging Exporting
    – Export again the posts
    – Check again the file wp-content/debug.log

    If this time the titles are OK, then it means one of the other plugins is causing the issue. If so, activate one plugin after the other and export again every time the posts until you find the plugin that is giving issues.
    Once you find the plugin, please tell me which plugin is the problem and I will try to reproduce the same problem on my installation.

    Freesoul Deactivate Plugins will disable the other plugins only during the exporting process, it will not do anything on the frontend if you don’t change the other settings.

    After the investigation, I suggest you remove the lines of code that you added to wp-config.php.

    I hope it helps.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Permalinks messed up’ is closed to new replies.