Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Steven Gliebe

    (@stevengliebe)

    Hello,

    I’m sorry, I didn’t see this until today.

    If you try deactivating all plugins then re-export your WIE file, are you able to import it into the other site? I am wondering if a plugin might be affecting the widgets data in some way. That error will show if the file is empty or if the data cannot be decoded.

    If that doesn’t work you can send me a copy of of your WIE file and I’ll test it, but please try deactivating plugins first. My email can be found at https://stevengliebe.com

    Plugin Author Steven Gliebe

    (@stevengliebe)

    Also try the import on the other site while all plugins are inactive just in case there is a plugin conflict on the importing end.

    I have the same problem but it’s really impossible to disable plugins as I have a wordpress network and plugins are enabled in the whole network.

    my plugins are:
    All In One WP Security
    Buddypress
    Clipboard images
    Comment email reply
    image watermark
    Pending Submission Notification
    Post Pay Counter
    Remove Google Fonts References
    Unyson
    User Role Editor
    W3 Total Cache
    Widget Logic
    WP Better Emails
    WP Smush
    myCred

    I tested on another wordpress installation which doesn’t have any plugins enabled and I didn’t see this error there and the plugin worked. but I don’t know which of the above plugins is affecting the widgets data.

    I also exported widgets from my wordpress multisite and tried to import them on the test wordpress installation (without plugins) and I encountered the same error. So the problem should be in exporting.

    Plugin Author Steven Gliebe

    (@stevengliebe)

    I also exported widgets from my wordpress multisite and tried to import them on the test wordpress installation (without plugins) and I encountered the same error. So the problem should be in exporting.

    That helps narrow it down a bit in your case. The original poster’s issue might be different or it might be the same.

    Since it works on the other install without other plugins, try adding the the other plugins to see if the issue starts happening. You could then deactivate all and enable one by one to determine which is causing the problem.

    Otherwise you could try network disabling the plugins very quickly so that the other sites are not affected very long. Or, try targeting one plugin at a time. I’d start with any that have something to do with widgets.

    Plugin Author Steven Gliebe

    (@stevengliebe)

    Did you have any luck with this?

    I did it manually with phpMyAdmin.

    Hi
    I disabled all the plugins except All In One WP Security but got the same error again

    I was wondering if the problem is with Persian characters! because my site is in Persian and I’ve used Persian characters in widgets. Also I have problem in doing it manually with phpMyAdmin and even SQL!! I changed all Persian words to English so that there weren’t any Persian character but I got the same error again.

    Plugin Author Steven Gliebe

    (@stevengliebe)

    Based on what you tested earlier, one of the plugins is probably causing the issue while exporting. If you did not deactivate All in One WP Security, then the problem might be with that plugin. Try deactivating all then export.

    I’m not sure if the problem is with Persian characters. I would think not but you could test by re-adding all your widgets with latin characters only then testing an export.

    Hi again
    I found the problem that I had with sql codes!
    I have a lot of text widgets and in them I have newLines. So I gave it a try and removed all the newLines from my widgets and tried again in exporting and the problem was solved.

    But I tested your plugin again and got the same error again ??

    Plugin Author Steven Gliebe

    (@stevengliebe)

    Could you please clarify. You say the problem is solved but then say that you get the same error so I am confused. If you’re editing the database directly instead of via WordPress, you might get unexpected results since the data might not be stored as WordPress expects.

    I said the problem was solved using SQL (in phpMyAdmin). I used UPDATE in SQL to update widget rows in wp_options table

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Import data could not be read. Please try a different file.’ is closed to new replies.