• Hi Camille,

    Thanks for the updated version. At my local server (with PHP 8.1.17) everything works fine. However, at my provider (live website) with PHP 8.1.20 I cannot activate Travelers’Map after the update.

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /www/wp-content/plugins/travelers-map/includes/admin/cttm-admin.php:374 Stack trace: #0 /www/wp-content/plugins/travelers-map/travelers-map.php(59): require_once() #1 /www/wp-admin/includes/plugin.php(2314): include_once('') #2 /data/sites/web/..../www/wp-admin/plugins.php(192): plugin_sandbox_scrape('travelers-map/t...') #3 {main} thrown in /www/wp-content/plugins/travelers-map/includes/admin/cttm-admin.php on line 374

    Do you have any idea why this could be happening?

    Tnaks in advance,

    Rob de Cleen

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Rob de Cleen

    (@rdc2701)

    Funny thing: I restored a backup from 24-06-2023 at my provider, and that already had v 2.2.0 running well. So for now (Cache from 24-06 is running) I don’t dare for now make any changes to the live website to deactivate/reactivate the plugin, but I may try that at a later date should the problem reoccur. I haven’t got a clue why the re-updated version would have thrown that error on trying to reactivate the plugin, but I thought you might want to know that it happened.

    Kind regards and thanks for you support,

    Rob

    Thread Starter Rob de Cleen

    (@rdc2701)

    Update: after a while the same problem occurred, all pages and posts started showing “Leaflet JS files missing”.

    Re-saving the TravelersMap config and clearing W3TC cache seems to put everything back in working order, so I hope that was the issue, that the config needed to be saved again. So this is solved for now, will keep you posted if it lasts.

    Have a good evening

    Rob

    • This reply was modified 1 year, 5 months ago by Rob de Cleen.
    Thread Starter Rob de Cleen

    (@rdc2701)

    I am happy to note that after restoring the site backup and saving the plugin config again, everything continues to work well. After some more thinking and testing the conclusion must maybe be that the plugin config on the live website somehow failed to save properly, resulting in the errors reported earlier.

    Maybe it would be nice if the color of the button could change when saving the TM plugin settings, so that it is visible that the saving went well?

    Thanks for your time and effort

    Rob

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Uncaught error 2.2.0 with PHP 8.1.20’ is closed to new replies.