13-Aug-2010, 03:40 AM
This thread is for validation bugs that you may find.
So far, I've found that line breaks create a <p> element where it can't go. This should be easily fixed by replacing <p> with <br>.
Another one is the possibility of someone entering an empty string for the anchor text under settings->processor->general. It is fixed with the following on line 200:
There also seems to be an issue with the validation error messages in the front-end. It occurs because there is a list in a span element. This could be fixed by replacing <span> with <div>, and adding "display: inline;" if required.
If you find any validation bugs, feel free to post them here.
So far, I've found that line breaks create a <p> element where it can't go. This should be easily fixed by replacing <p> with <br>.
Another one is the possibility of someone entering an empty string for the anchor text under settings->processor->general. It is fixed with the following on line 200:
PHP Code:
<?php if($anchor_text != null && $anchor_text != ""){ ?><a name="<?php echo $anchor_text?>"></a><? } ?>
There also seems to be an issue with the validation error messages in the front-end. It occurs because there is a list in a span element. This could be fixed by replacing <span> with <div>, and adding "display: inline;" if required.
If you find any validation bugs, feel free to post them here.
I'm giving you three guesses...