Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2006-09-21 19:28:17

David_1cog
Member
From: Bristol, England
Registered: 2004-09-09
Posts: 58
Website

r1835 - Diagnostics parse error

Clean install of r1835 to localhost. All seemingly OK, but when I click ‘Diagnostics’:

Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING in C:\_LOCALHOST\xampp\htdocs\textpattern\include\txp_diag.php on line 260


David @ 1 Cog
“Follow the shoe!” … “No, follow the gourd!”

Offline

#2 2006-09-21 21:47:54

wet
Developer Emeritus
From: Vöcklabruck, Austria
Registered: 2005-06-06
Posts: 3,391
Website GitHub Mastodon

Re: r1835 - Diagnostics parse error

Not reproducable here.

Offline

#3 2006-09-21 21:52:58

zem
Developer Emeritus
From: Melbourne, Australia
Registered: 2004-04-08
Posts: 2,579

Re: r1835 - Diagnostics parse error

Sounds like your copy has been modified or corrupted.


Alex

Offline

#4 2006-09-21 23:28:42

David_1cog
Member
From: Bristol, England
Registered: 2004-09-09
Posts: 58
Website

Re: r1835 - Diagnostics parse error

Alex,

No, it’s fresh from SVN and unmodified. I just checked out the 4.0 branch again and compared with what I’m running – identical.


David @ 1 Cog
“Follow the shoe!” … “No, follow the gourd!”

Offline

#5 2006-09-21 23:36:59

zem
Developer Emeritus
From: Melbourne, Australia
Registered: 2004-04-08
Posts: 2,579

Re: r1835 - Diagnostics parse error

What’s on line 260 of that file?

I’d guess you’ll see some Subversion conflict markers.


Alex

Offline

#6 2006-09-22 09:51:03

David_1cog
Member
From: Bristol, England
Registered: 2004-09-09
Posts: 58
Website

Re: r1835 - Diagnostics parse error

I downloaded / installed latest TortoiseSVN, checked out again (got r1838 this time), exported. Still the same.

I then compared txp_diag.php from the ’4.0-20060831.zip’. Line 260 (<code>if (preg_match(‘@^(\S+): r?(\S+) \((.*)\)$@’, trim($c), $m)) {</code>) still the same but line 247 shows:

<code>if (preg_match(‘/^\$LastChangedRevision: 1787 $line, $match)) {</code> – my r1838<br /><code>if (preg_match(‘/^\$LastChangedRevision: (\w+) \$/’, $line, $match)) {</code> – 4.0-20060831.zip<br />
Replacing that line solves the problem. Is it my checkout with Tortoise causing the problem? Any idea how I prevent it happening?

Last edited by David_1cog (2006-09-22 09:56:25)


David @ 1 Cog
“Follow the shoe!” … “No, follow the gourd!”

Offline

#7 2006-09-23 00:23:49

zem
Developer Emeritus
From: Melbourne, Australia
Registered: 2004-04-08
Posts: 2,579

Re: r1835 - Diagnostics parse error

Is it my checkout with Tortoise causing the problem? Any idea how I prevent it happening?

It could be. Tortoise might be incorrectly inserting svn keyword info on that line. Here’s what it should look like:

http://dev.textpattern.com/browser/development/4.0/textpattern/include/txp_diag.php#L247


Alex

Offline

#8 2006-09-23 05:11:05

Mary
Sock Enthusiast
Registered: 2004-06-27
Posts: 6,236

Re: r1835 - Diagnostics parse error

That’s weird, David, I’ve never had this problem with TortoiseSVN.

When you’re doing the new checkout: is this into a brand new folder? I’m wondering if the svn database for that folder might be corrupted?

Offline

#9 2006-09-23 13:55:26

David_1cog
Member
From: Bristol, England
Registered: 2004-09-09
Posts: 58
Website

Re: r1835 - Diagnostics parse error

Mary,

That occurred to me – I deleted my ‘svn’ folder and checked out again. Same result.

Just started from scratch once more – problem is now solved (might be something to do with log showing ‘zem – stop bogus LastChangedRevision keyword replacement’ ;)).

Thanks all.


David @ 1 Cog
“Follow the shoe!” … “No, follow the gourd!”

Offline

Board footer

Powered by FluxBB