Thread

Feel free to shoot me down if this isn’t a valid bug because it could be caused by either EE or caused by the Structure Module.

It looks like {page_uri} isn’t being parsed in the weblog:entries loop. This is the first time I’ve experienced this.

My exp_sites|site_pages serialized array looks something like:

Array
(
[1] => Array
(
[uris] => Array
(
[18] => /contact_us/
)

[templates] => Array
(
[18] => 22

)

[url] => <a href="http://example.com/">http://example.com/</a>
)

)

I notice that (what I assume is a new 1.6.9 update) the exp_sites|site_pages array is held within an array using the site_id as an array key.

The Weblogs Module at line 3263 handles {page_uri}

if ($site_pages !== FALSE && isset($site_pages['uris'][$row['entry_id']]))
   {
     $row['page_uri'] = $site_pages['uris'][$row['entry_id']];
      $row['page_url'] = $FNS->create_url($site_pages['uris'][$row['entry_id']]);
   }

and edited as such

if ($site_pages !== FALSE && isset($site_pages[$row['site_id']]['uris'][$row['entry_id']]))
            {
                $row['page_uri'] = $site_pages[$row['site_id']]['uris'][$row['entry_id']];
                $row['page_url'] = $FNS->create_url($site_pages[$row['site_id']]['uris'][$row['entry_id']]);
            }

Adding the $row[‘site_id’] solved the issue on this particular site.

So my question is, is the exp_sites|site_pages array supposed to be formatted this way as of 1.6.9 and is this bug valid?

stephenfrank,

In EE 1.6.9’s version notes it specifically mentions Structure and the need to upgrade that along with EE. Can you upgrade to latest Structure and see if bug remains.

Thanks,

I’ve since found that it was a botched upgrade to 1.6.9 that caused the problem. The Weblog module files were not properly overwritten (specifically the lines around line 3263 being the problem).

-Stephen

Glad you found the culprit!