Define Pages problem (after upgrade)

[RodG]

Hi Guys,

I thought I'd seen them all, but I'm working on a site update and have hit a snag that I've not managed to solve yet (and am about to head off to bed).

Problem, when testing the define pages editor it seems to fail to import the existing file(s).

The override folders are being used is per the following.

Editing file:
/home/xxxxx/public_html/store/includes/languages/english/html_includes/freetemplate3/define_contact_us.php

The already edited page is displayed by the store as it should be, but the edit box is devoid of any data. This is using both plaintext and the ckeditor (which I've reinstalled)

The strange thing is, if I 'edit' the blank page with a 'Hello World" and save it, all is working fine.. I see the newly edited page from the front end, and I can re-edit the page without any problem. I've verified that the edited page is indeed overwriting the original file at
/home/xxxxx/public_html/store/includes/languages/english/html_includes/freetemplate3/define_contact_us.php so there is something amiss with the reading of the original files (The problem occurs with all define editor pages, not just the contact page.

There's nothing in the log files to suggest anything is going wrong.

Any ideas?

Cheers
Rod

[lhungil]

Not sure 100% of the cause, but as a workaround you may be able to simply "copy" from the source file, "paste" into the define text editor, and save. This may get you up and running and allow you to edit the define pages in the future.

If nothing else I would try this on at least one page (keeping a backup of the original define page)... And then do a file comparison to see what is different between the original and the new one... Maybe some difference can be spotted which will help (Character encoding? Line terminators? EOF / NULL character out of place)?

[stevesh]

Any chance it's a browser issue ? Looking through the forum, it looks like a character set mismatch will cause that, too.

[DrByte]

The already edited page is displayed by the store as it should be, but the edit box is devoid of any data.

As stevesh said, that's a classic symptom of charset mismatch.

[RodG]

Thanks Guys. Problem solved.

It was a character set mismatch, and I have to blame myself for this one.

When I'd made the change to keep iso-8859-1/latin1 I somehow managed to use a ` rather than a' (what can I say.. it'd been a long day and I was tired)
(backtick vs single quote)

Apologies to all, and thanks again.

Cheers
Rod

[RodG]

Hi Guys,

I've just found another strange problem with my latest site upgrade.

Neither of the shippinginfo and conduct_us show up. Both produce a 'page not found' error, but only when the store is live. If I switch it back to "Down for maintenance" there's no problem.

Any ideas?

Cheers
Rod

[RodG]

Hi Guys,

I've just found another strange problem with my latest site upgrade.

Neither of the shippinginfo and conduct_us show up. Both produce a 'page not found' error, but only when the store is live. If I switch it back to "Down for maintenance" there's no problem.

Any ideas?

Cheers
Rod

I'm still struggling with this. I also need to add the 'Privacy Notice' to the list. Again, only when the site is live. All is fine when Down for maintenance.

I'm really stumped. What is it about being in maintenance mode that could be preventing a problem that shows on the live site? I've also not been able to determine exactly what the filename is that is causing the error. Nothing in any of the logs. There's no URL rewriting tools installed.

Cheers
Rod

[dbltoe]

RodG,
In another thread, it was found that the culprit for the mismatch was a define file for the template. It was not in an area that the DTK searched.
Maybe that's the culprit in your case as well.

[RodG]

RodG,
In another thread, it was found that the culprit for the mismatch was a define file for the template. It was not in an area that the DTK searched.
Maybe that's the culprit in your case as well.

I'm not discounting this (in fact I'm not discounting anything at the moment), but if it were a template/define problem I'd be expecting to be seeing the same issue when both live and in maintenance mode, because the same templates/defines are being used in both cases.

Obviously I'm missing some important factor here, but I'm just not seeing what it is. Are there modules (or something) being activated in live mode that are *not* being activated in maintenance mode that are causing a conflict? If so, which ones?

I'm starting to think I'm going to have to bite the bullet on this one and install a copy of the site locally, then step through the code line by line. (At the moment I'm working on a copy on the clients server).

Cheers
Rod