I am getting a the following message on the W3C validator:
Character Encoding mismatch!
The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation.
This is with a default install.
Thanks
Quote from: rogalsky at Nov 18, 2006, 12:00 PM@rogalsky: I am unable to reproduce this problem. I believe you are still doing something wrong during installation. Did you make sure your manager/includes/config.inc.php file was updated during the upgrade installation process? Those constants causing the errors in your original description were added to this config file in these latest versions and that file must be updated during the upgrade.
I download and install lastest version from trunk SVN - MODx 0.9.5 RC3 rev2032.
My problem was kept, but i don’t know how to open a bug tracker report.
I badly know English language. Please open it self. Thanks!
Here i post my problem - http://modxcms.com/forums/index.php/topic,8612.msg63744.html#msg63744
@OpenGeek. This time I did not do upgrade. I have made installation modx with sample data on my local server. When I have taken a file tv.ajax.php from modx rc1 - the problem was solved.
My server: Apache 1.3.33 php5.1.2. php_flag register_globals Off
Then that’s why it doesn’t work. If you don’t do the upgrade it won’t.I think he meant that he had done a clean install - I’ve checked tv.ajax.php and found that the config.inc.php was prepended with the MODX_BASE_PATH which at that point isn’t defined. The config.inc.php has to be included relatively - I’ll get it committed to SVN shortly.

Quote from: Gaia at Nov 20, 2006, 02:14 PM
There seems to be a stuck loop or refresh or something. I updated the site Configuration and it just keep refreshing at the following page:
Action was completed successfully!
- Please wait while MODx cleans up.
That and not all of my documents are listed to the left?
Thanks.
Not sure if it’s related, but a few days ago, after an edit, the "main content frame" was reloaded with nested left/top navigation, resulting in 2 document trees, etc...
I have not been able to replicate since, and have tried. I possibly clicked/submitted prior to the previous xmlhttprequest completing...possible overlap?
hey. I fixed my problem by deleting everything from the /manager/ folder ( except config.php ) and re-uploaded the RC /manager/ files. Works prefect now
Quote from: garryn at Nov 20, 2006, 03:11 PM
Hi Gaia, could you please post your server configuration details (PHP version etc.), and which MODx RC/SVN revision number you’re running and which browser you’re using. Thanks!
Sure, here is some info, if you need to know something else, just ask.
MODx version - 0.9.5 RC2
Version codename - rev 1942
PHP Version - 4.4.2
MySQL Version - 4.1.21
Browser - FireFox 2.0
.
Hi Ryan, no I don´t have a more recent version. But this error was fixed by the "line feed" problem in confic.php (see other thread). So everything´s fine now
Quote from: MadeMyDay at Nov 14, 2006, 05:16 AM
New installation doesn´t work on this server. So I think it definitively has something to do with the PHP/MySQL version or some other settings. Btw: 0.92 went fine there.
"working server" has:
PHP Version 4.4.4 (register globals OFF)
PHP Version 5.1.6 (register globals OFF)
Not working (for me):
PHP Version 4.4.1. (register globals ON)
But unfortunately the setting of register_globals to "off" didn´t work either. How is your setting there?
Marc, have you been able to test a more recent SVN trunk version than RC2 with this?
The included theme has a reference to page #11 as an rss 2.0 feed, which it does not seem to be. I remember there being code for this from looking over stable - does this just need to be included in the installer again?
Quote from: rthrash at Nov 29, 2006, 03:57 PM
Where in the included theme is there a reference to 11 as an RSS feed?
It gets better and better! Under 4 minutes from downloading rc3 zip to having a 1st class, state of the art CMS up and running local winXP/XAMPP. Keep up the good work!
Just a couple of points I noticed straight away:
1 - Before the install I am asked what ressources to install/update - default is everything. Since I find Quick Edit just gets in the way on dev sites, I unchecked
AND
- Modules
- Install/Update QuickEdit - Renders QuickEdit links in the frontend
- Plugins
- Install/Update QuickEdit - Front-end Content Editor
Questions: is Quick Edit a Module, a Plugin or both? Is one of these options redundant? In any event, Quick Edit was not showing up at front-end as intended, whilst appearing to be installed and enabled in Manager/Modules/Manage Modules. All very confusing.....
The module handles the authentication bits for the manager users, and the plugin handles the rendering of the various QE bits in the front end.
Quote from: rthrash at Nov 29, 2006, 08:47 AM
The problem is that there’s a serious bug in the way Opera handles some of the CSS. (...)
So it’s still stands as needing a custom theme. Unless you can keep the block and full height left-border on the top-level menus that is.
OK. I took a closer look at the CSS and I think I have fixed thatThe problem was the CSS itself. The resolution is in the patch attached to this message (I had to change the file extension to .txt to attach it).
FS#702 — Fix manager menu tabs to work with Opera in MODxLight theme
I made also few minor corrections.

This discussion is closed to further replies. Keep calm and carry on.