Thread

I was going to be updating a client’s website to 1.7.0, but thought I’d go to 1.7.1 seens as it was released. Unfortunately I’m now experiencing a really strange error when trying to view any content on the website other than the home page.

When view a page, this is the error I receive (Note: username and system names have been changed in error message provided below):

Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/userxxx/public_html/systemdir/modules/weblog/mod.weblog.php on line 7005

I have since slipped v1.7.0 of the weblog module back into the /systemdir/modules/weblog/... directory, and it’s working again.

As I’ve already applied the 1.7.1 fix to the database, will rolling back to the 1.7.0 files only cause any problems or do I need to go back to my previous version of the database and update that way?

Thanks
Brendan

I am seeing this as well, however, I see it when I attempt to run the update after installing all new files.

Hmm, weird. I did manage to get it to update fine. What version were you updating from? I was going from v1.6.9.

I was updating from 1.6.9 as well. I am going back to 1.7.0 until this is resolved.

Wondering if that’s what’s causing problems that I’m having with WYGWAM as well. How are you rolling back to 1.7.0? I are reimporting a backed up database, or just rolling back to 1.7.0 files?

Because the update didn’t complete I simply replaced the core folders and files with 1.7.0 versions and then ran the update.

OK, bugger. So that options not really open to me. Let’s see what Ellis Lab says.

sillbeer,

I just let the devs know on this one.
According to Google T_PAAMAYIM_NEKUDOTAYIM is Hebrew for “missing double dots” so looks to be just a simple case of sytax in the module maybe.

We will reply here when we hear back. Thanks for your patience and sorry for inconvenience

Well looking at line 7005 that it relates to, it’s something that was changed:

v1.7.1

if (strpos($TMPL->tagdata, LD.'title') !== FALSE)
        {
            $TMPL->tagdata = str_replace(LD.'title'.RD,  $TYPE::format_characters($query->row['title']), $TMPL->tagdata);        
        }

        if (strpos($TMPL->tagdata, '_entry->title') !== FALSE)
        {
            $TMPL->tagdata = preg_replace('/'.LD.'(?:next|prev)_entry->title'.RD.'/', $TYPE::format_characters($query->row['title']), $TMPL->tagdata);
        }

v1.7.0

if (strpos($TMPL->tagdata, LD.'title') !== FALSE)
        {
            $TMPL->tagdata = str_replace(LD.'title'.RD, $query->row['title'], $TMPL->tagdata);        
        }
        
        if (strpos($TMPL->tagdata, '_entry->title') !== FALSE)
        {
            $TMPL->tagdata = preg_replace('/'.LD.'(?:next|prev)_entry->title'.RD.'/', $query->row['title'], $TMPL->tagdata);        
        }

Apologies to all- the error happens PHP < 5.3, hence the inability to replicate it by JH.

For a short term fix- edit mod.channel.php on lines:
7005

if (strpos($TMPL->tagdata, LD.'title') !== FALSE)
{
    $TMPL->tagdata = str_replace(LD.'title'.RD,  $TYPE->format_characters($query->row['title']), $TMPL->tagdata);        
}

Line 7008

if (strpos($TMPL->tagdata, '_entry->title') !== FALSE)
{
    $TMPL->tagdata = preg_replace('/'.LD.'(?:next|prev)_entry->title'.RD.'/', $TYPE->format_characters($query->row['title']), $TMPL->tagdata);
}

In other words- switch $TYPE::format_characters to $TYPE->format_characters.

Should do the trick and we’ll work on getting a fix in.

Hi Robin, I assume you mean mod.weblog.php?

Ack- sorry!  Yes mod.weblog.php.

And this has been hotfixed in the current download.  Sorry you were bitten by this bug!

If you haven’t yet applied this fix, you can do so by downloading the latest version and replacing one file: system/modules/weblog/mod.weblog.php.

That get you guys up and running?

Hi,

I just updated EE from 1.6.9 to 1.7.1 and I’m experiencing errors too.

I’m getting code in at the top of my page and where my navigation should be “c831adif9wel5ed9e” if my site is turned on (it’s not there if I have the site off and my offline page is showing).  When I first tried accessing the front end of the site I received another code “a6b2eT3…” but once I logged out and logged back in as the Super Admin I couldn’t get any of the front end pages to show.

I then downloaded and installed the new “mod.weblog.php” as suggested and the only fix this solved was an extremely slow CP and nothing showing up on the front end.  I’m still getting code at the top of the page.

I tried disabling all extensions via the config.php file but that didn’t help.

Any suggestions?

Thanks.
Lori