Re: BUG in 3.2.8: Errors in generated button markup

2010-10-25T22:13:00-05:00

Hi there. Thanks for reporting this important issue.

Not to worry, this is the intended behavior. s2Member's application of HTML comments within your Button Code is expected, and it is perfectly valid HTML markup. Please see:
http://www.tizag.com/htmlT/htmlcomments.php

Code:

This is valid HTML markup for a comment.

Now, if you're seeing comment lines in the output of your code, that would indicate to me that your Button Code is becoming corrupted in some way. It is not uncommon for this to happen with the Full Button Code, because the WordPress® Visual Editor often causes conflicts with raw HTML code. I've also seen corruption caused by output filters applied by WordPress® itself. This is why the Shortcode format is recommended.

So it sounds like there is something in your WordPress theme, or possibly a conflict with the Visual Editor that is causing this. You might give this plugin a shot RAW HTML ( http://wordpress.org/extend/plugins/raw-html/ ).

If the Full Button Code continues to give you trouble, you might try adding it into a theme file directly. If none of that works for you, you may have to revert back to using the Shortcode format supplied by s2Member. Please let us know if you need further assistance on this topic.

Statistics: Posted by Jason Caldwell — October 25th, 2010, 10:13 pm

BUG in 3.2.8: Errors in generated button markup

2010-10-25T14:44:24-05:00

The HTML generated by the plugin has a bunch of lines in it that look like this:

Code:

...which is incorrect.
The full HTML tag within the comment ends up breaking the comment tag itself, with the result that the rendered page looks like this:

Code:: –> –> –> [button image]

(The commenting is done three times in my case, possibly different for different settings.)

The same bad markup comes out of using the shortcodes.

Statistics: Posted by sugeneris — October 25th, 2010, 2:44 pm

Community Support Forums

Re: BUG in 3.2.8: Errors in generated button markup

BUG in 3.2.8: Errors in generated button markup