• Resolved siteshack

    (@siteshack)


    Hi
    It seems that Web Stories creates super long filenames for the stories. This prevents musing migration tools and backup tools. As you can’t export the stories eith I am left with two site I can not migrate without deleting the stories
    Extremely annoying

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Pascal Birchler

    (@swissspidy)

    Hi there,

    With filenames, do you mean the final story URL like https://example.com/web-stories/url-to-your-story/? WordPress by default uses your story title to generate this URL, but you can change it and shorten it in the “Document” section under “Permalink”.

    Thread Starter siteshack

    (@siteshack)

    Hi I get this error I have ……… the site name

    Critical Transfer Error
    Uncaught PharException: tar-based phar "............/wp-content/uploads/1631707677-237223961d192dc8d8e00c3896f7f46e551c4585/plugins/web-stories.tar" cannot be created, filename "assets/js/vendors-chunk-getStoryPropsToSave-chunk-resize-observer-polyfill-wp-story-editor-d59b0d3bf030486d0bb2.js" is too long for tar file format in ......../wp-content/plugins/siteground-migrator/includes/class-siteground-migrator-files-service.php:205 Stack trace: #0 .........../wp-content/plugins/siteground-migrator/includes/class-siteground-migrator-files-service.php(205): PharData->buildFromDirectory('/home/556511.cl...') #1 ........../wp-content/plugins/siteground-migrator/includes/class-siteground-migrator-files-service.php(146): Siteground_Migrator_Files_Service->create_encrypted_archive('/plugins/web-st...') #2 ......../pub in /home/556511.cloudwaysapps.com/bpenqeeewx/public_html/wp-content/plugins/siteground-migrator/includes/class-siteground-migrator-files-service.php on line 205
    Thread Starter siteshack

    (@siteshack)

    Oh and BTW I have tried renaming it but it get auto regenerated. Many Thanks

    Thread Starter siteshack

    (@siteshack)

    Lastly

    I did uninstall it and then migrate and reinstalled the plugin on the new host and all data and stories was there. So that was handy. This leads me to say that it would therefore be better to have a setting that would make it an option to keep or delete all tables/data on deletion.

    So I’m happy but it took a bit or sorting and I’m not sure its best practice currently

    Thanks

    Plugin Author Pascal Birchler

    (@swissspidy)

    Thanks for your additional feedback. The file name indeed seems a bit long, I’ll see how we can shorten those a bit .

    Also very good point regarding the uninstall.

    By default we retain all data unless opted out via the web_stories_erase_data_on_uninstall filter. We’re considering adding a UI option for this though on the settings page. Would that work for you?

    Is there anything else we could help you with? If so, just let us know here or perhaps by leaving a review.

    Thanks!

    Thread Starter siteshack

    (@siteshack)

    Yep UI option just the ticket. Would still need explaining somewhere that you can migrate the way I did it though but if you fix the file name length then I guess migrations will work ??

    @siteshack Thank you for the feedback! This topic will be resolved but please feel free to monitor the GitHub ticket for any progress on the matter.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Long file name stops migration’ is closed to new replies.