Errors and issues upgrading from Cooked Classic

  • Resolved seoidau

    (@seoidau)


    8 years, 6 months ago

    Hello

    In a localhost test environment, I have followed your instructions to migrate from the original Cooked Classic. However I haven’t progressed to the ‘purchased’ Cooked Pro (also successfully completed) to see if I can get away with using just the Free version and not the Pro.

    The recipe page (frontend) then fills with maaaaaaaaany instances (screens and screens) of

    Warning: rand() expects parameter 1 to be integer, float given in C:\xampp\htdocs\xxxxxxxxxx\wp-content\plugins\cooked\includes\class.cooked-recipes.php on line 961

    It also does this in the recipe editing page, but disappears when I click on ‘Update’ to save it. That instruction to click Update appears after the warning is repeated 16 times for line 961 (as above) and 13 times for line 990.

    Unfortunately also all recipe content is lost except the last section heading used – no ingredients nor directions, just a single section heading.

    Is this caused because I am trying to migrate from Cooked Classic to Cooked Free, and I should be migrating to Cooked Pro only?

    (Also, if so, would I be able to install Cooked Pro on a local test environment as well as a live site at the same time?)

    • This topic was modified 8 years, 6 months ago by seoidau.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Boxy Studio

    (@boxystudio)

    8 years, 6 months ago

    You don’t need Cooked Pro to do the update from Classic to this version. However, it sounds like you’ve entered your old recipe ingredients in as line items instead of using the drag and drop editor? I’m thinking there might be a bug that is conflicting with the “per line” entered ingredients from Classic. Can you confirm that this is the case?

    Thread Starter seoidau

    (@seoidau)

    8 years, 6 months ago

    The recipes were originally entered in the Detailed Entry view, not the Simple Entry view – both ingredients and directions.

    Plugin Author Boxy Studio

    (@boxystudio)

    8 years, 6 months ago

    Honestly I’m not sure what is going wrong here without being able to take a closer look. Can you shoot me an email so we can discuss further?

    support@cooked.pro

    Thanks!

    Thread Starter seoidau

    (@seoidau)

    8 years, 6 months ago

    I have emailed you as requested. Issues are still persisting even on a fresh new local test environment.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Errors and issues upgrading from Cooked Classic’ is closed to new replies.