WordPress.org

Forums

Widget Settings Importer/Exporter
[resolved] Error "Filename cannot be empty" while importi (7 posts)

  1. Cyrus180
    Member
    Posted 2 years ago #

    Hey there,

    I want to export my widget settings from an Online-Server into my local environment. The export works fine. The JSON-File isn't empty. However everytime I try to import the JSON-File/click on the "Show Widget Settings", I get the error message "Warning: file_get_contents() [function.file-get-contents]: Filename cannot be empty in [...]\wp-content\plugins\widget-settings-importexport\widget_data.php on line 373". After that I get the buttons Select/Un-Select All Widgets but there is no content.

    Any idea where the problem could be?

    http://wordpress.org/extend/plugins/widget-settings-importexport/

  2. mvadar
    Member
    Posted 2 years ago #

    I am experiencing the same issue running WP 3.4.1. I select the JSON and click the 'Show Widget Settings' once and nothing happens. Upon clicking the button a second time, I receive the same error message listed above.

    Anyone else?

  3. mvadar
    Member
    Posted 2 years ago #

    Going to open myself to public ridicule by admitting a simple mistake so that others may benefit from my experience: At the time of my previous post, I had only tried this in IE9 (9.0.8112.16421). I have since tried in Firefox and the operation completed successfully.

  4. idahopcsolutions
    Member
    Posted 2 years ago #

    mvadar... Man.. You saved me, that was driving me crazy.
    Thank you!

  5. mukeshwani
    Member
    Posted 2 years ago #

    I've tried Firefox and Safari, same error. Why would this be a browser issue? mvadar is this plugin only supporting Firefox, I must of missed that somewhere because using a browser shouldn't be a "mistake" so don't blame yourself.

    Looks like the plugin doesn't work with wp 3.4.1. I upgraded to 3.5 and the import functionality worked.

  6. Kevin Langley
    Member
    Plugin Author

    Posted 2 years ago #

    I've tested in IE8 and 9 and haven't found any issues using 3.4 or 3.5 and the latest version of the plugin. Is anyone still experiencing any?

  7. Kevin Langley
    Member
    Plugin Author

    Posted 2 years ago #

    Marking as resolved as I am no longer able to replicate and have gotten no responses from users experiencing the same issue.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic