THE MOLITOR FORUMS » Topic: Illegal string offsets when adding new entries http://www.themolitor.com/forums/topic/illegal-string-offsets-when-adding-new-entries THE MOLITOR FORUMS » Topic: Illegal string offsets when adding new entries en-US Tue, 28 Apr 2026 20:58:19 +0000 http://bbpress.org/?v=1.1 <![CDATA[Search]]> q http://www.themolitor.com/forums/search.php THE MOLITOR on "Illegal string offsets when adding new entries" http://www.themolitor.com/forums/topic/illegal-string-offsets-when-adding-new-entries#post-25687 Thu, 19 Dec 2013 14:06:52 +0000 THE MOLITOR 25687@http://www.themolitor.com/forums/

Hi there,

Can you provide a link to your site? I'll check it out.

Best,

Chris

Shallnotbe on "Illegal string offsets when adding new entries" http://www.themolitor.com/forums/topic/illegal-string-offsets-when-adding-new-entries#post-25686 Thu, 19 Dec 2013 13:47:48 +0000 Shallnotbe 25686@http://www.themolitor.com/forums/

Hi Chris,
Thanks for the quick reply.
Good news: it's ok for the single post, the message doesn't show up anymore. ;)
Bad news: the main map and the tag maps related to the post are still grey. :(
Tried on different browsers, still grey.

THE MOLITOR on "Illegal string offsets when adding new entries" http://www.themolitor.com/forums/topic/illegal-string-offsets-when-adding-new-entries#post-25684 Thu, 19 Dec 2013 13:23:26 +0000 THE MOLITOR 25684@http://www.themolitor.com/forums/

Hi there,

Try this... Open up single.php and change the following on lines 33-41 from this...

//LEGACY SUPPORT
$data = get_post_meta( $post->ID, 'key', true );
$oldZoom = $data['zoom'];
$oldLatitude = $data['latitude'];
$oldLongitude = $data['longitude'];
$oldAddrOne = $data['address_one'];
$oldAddrTwo = $data['address_two'];
$oldPin = $data['pin'];
$oldBg = $data['bg_img'];

...to this...

//LEGACY SUPPORT
$data = get_post_meta( $post->ID, 'key', true );
if(isset($data['zoom'])){$oldZoom = $data['zoom'];}
if(isset($data['latitude'])){$oldLatitude = $data['latitude'];}
if(isset($data['longitude'])){$oldLongitude = $data['longitude'];}
if(isset($data['address_one'])){$oldAddrOne = $data['address_one'];}
if(isset($data['address_two'])){$oldAddrTwo = $data['address_two'];}
if(isset($data['pin'])){$oldPin = $data['pin'];}
if(isset($data['bg_img'])){$oldBg = $data['bg_img'];}

Let me know if that works.

Best,

Chris

Shallnotbe on "Illegal string offsets when adding new entries" http://www.themolitor.com/forums/topic/illegal-string-offsets-when-adding-new-entries#post-25678 Thu, 19 Dec 2013 12:52:39 +0000 Shallnotbe 25678@http://www.themolitor.com/forums/

Hi,

I've got issues with Navigator: I can't properly add new entries.
I only updated existing posts recently, and my problem appears at least on 1.7.3 & 2.0.1.

When I add a new entry, it adds a series of error messages before displaying the title.
Since that post is corrupted, it's impossible to show the main map as well, which is now grey.

Here's what it shows on a newly created post (I edited the path for privacy reasons):

Warning: Illegal string offset 'zoom' in /home/****/wpnavigator/single.php on line 35

Warning: Illegal string offset 'latitude' in /home/****/wpnavigator/single.php on line 36

Warning: Illegal string offset 'longitude' in /home/****/themes/wpnavigator/single.php on line 37

Warning: Illegal string offset 'address_one' in /home/****/themes/wpnavigator/single.php on line 38

Warning: Illegal string offset 'address_two' in /home/****/themes/wpnavigator/single.php on line 39

Warning: Illegal string offset 'pin' in /home/****/themes/wpnavigator/single.php on line 40

Warning: Illegal string offset 'bg_img' in /home/****/themes/wpnavigator/single.php on line 41

TITLE

Breadcrumbs / Breadcrumbs
Details
Address

It's like it's still trying to use the legacy data.

When I edit the post, on the custom fields panel I only see the new data: themolitor_address_one + two, themolitor_latitude + longitude...

I don't think I added new entries since the switch to the new system, so I don't know when the problem would have appeared. I only know for a fact that it shows up on 1.7.3 & 2.0.1.