Viewing 7 replies - 1 through 7 (of 7 total)
  • Hey Touda,

    It looks like your on the old Download Monitor (3.x), the latest version is 1.8.0. You can use our Legacy Importer to move your website to the new version: https://www.download-monitor.com/extensions/dlm-legacy-importer/

    Kind Regards,

    Barry Kooij

    Thread Starter Touda

    (@touda)

    Yes, that seemed strange to me. That 1.8.0 was newer than 3.x! ?? Thanks. We’ll try that importer.

    Thread Starter Touda

    (@touda)

    Isn’t it available at WordPress plugin repository? Must we go through the “add to cart” process? :-/

    Thread Starter Touda

    (@touda)

    Please de-activate the old Download Monitor plugin and activate the new Download Monitor plugin before continuing with the import. This will ensure the required post types and taxonomies exist prior to the migration.

    I understand that we must we have the new plugin installed?

    Thread Starter Touda

    (@touda)

    When trying to install the new plugin (downloaded via the blue button under the cat picture) we get an error:

    telling that /home/upbpfeul/public_html/d-3/democraciadirecta/wp-content/plugins/download-monitor/ directory already exist.

    then we proceed to deactivate the old plugin, but we get the same error message and installation fails.

    Are we supposed to delete the old plugin? Won’t it delete the tables we want to import from the new plugin?

    This process is very confusing! :-/ Shouldn’t it all be automatically done?

    Thread Starter Touda

    (@touda)

    It was solved just renaming the old directory without having to delete the old plugin. You might want to be clearer instructions for this import process. Thank you!

    New plugin is working OK and warnings have disappeared.

    Hey Touda,

    Yes the old plugin should be removed and the new one should be installed. I agree that this whole process is very confusing and I’m looking into creating an update that will get everyone on the same version again.

    Sorry about the confusion, glad to hear you’ve figured it out.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Warning: Creating default object from empty value’ is closed to new replies.