Verify page not working

So far I’ve got MODx working pretty good, apart from one thing; the veriword page. bS (or someone else, not totally sure anymore) posted that this error occured earlier, but sadly I haven’t been able to find it.

MODx version info:
MODx version 0.9
Version codename rev 1005
Misc version info:
PHP version = 5.1.1 apache2handler
Web server = Apache/2.0.59 (Unix)
Database = mysql 5.0.24-standard
GD Support enabled
GD Version bundled (2.0.28 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.1.9
Example: here.

So far I haven’t had any trouble with GD so I suppose it’s running fine, also I’ve double-checked all options in the manager menu, but I couldn’t find any clear cause of this.

Hopefully anyone here can supply me with a clue of how to fix this

does that veriword thing use the modx weblink feature somehow at some point.. anyways, there was a bug in the weblink feature that did just that, just displayed the url in a blank page.. I’m not sure if it’s related, but you can find a fix for that in the known issues thread.. try searching in google using "site:modxcms.com weblink known issues" as keywords (without quotes)..

Quote from: doze at Oct 19, 2006, 09:16 AM

does that veriword thing use the modx weblink feature somehow at some point.. anyways, there was a bug in the weblink feature that did just that, just displayed the url in a blank page.. I’m not sure if it’s related, but you can find a fix for that in the known issues thread.. try searching in google using "site:modxcms.com weblink known issues" as keywords (without quotes)..

Thanks for your reply, but the solutions for this problem seem to have been added already; the document.parser.class.php seems to have been patched already. Talking about this solution.

Edit; just noticed this one, going to take a look at that in a min, it solved my problem perfectly; really hoping this will be added into an updated beta release asap (together with other bugsfixes) as this bug seems to be quite old already.

Quote from: Leftblank at Oct 19, 2006, 12:30 PM

it solved my problem perfectly; really hoping this will be added into an updated beta release asap (together with other bugsfixes) as this bug seems to be quite old already.

it is fixed in betas already. both of em.

Quote from: doze at Oct 19, 2006, 01:30 PM

it is fixed in betas already. both of em.

Well, I suppose something got messed up with uploading the beta then, as I upgraded yesterday.