What the site does or does not recognize ... seems to be conflicting with Apophysis parameters sent via PMs.

Very recent change.


As *< flame > and **< / flame > (eliminate the spaces) ... are not recognized.

"(1:1) Error: * .. is not recognized!
(1:1) Warning: discarding unexpected ..** "

Time and opportunity permitting, perhaps this can be addressed?


(p.s. Haven't tried posting parameters to a discussion thread.)

Previewed this following comment;

"More ... please. Sincerely.


Caveats?

Lil' ... lil' soft on the focus.

Would be interesting/fun ... to play around with the DOF some more on this one.

And then again, there is the B & W possibilities.


Nice one, Jim. I really like the composition, textures and colours within frame.

And the lines of the gear itself work well on the note of leading lines in conjunction with your composition.

Thanks for sharing this one with us. :o)"


Came back with;

(1:232) Warning: unescaped & which should be written as &


/\ Nooo idea of it's relevance to this thread. Just some more stuff for you to read.

:oP

Made a link and used "Preview this comment" it came back with this....


(1:52) Warning: unescaped & or unknown entity "&feature"

Previewed this comment too....

Came back with:

Comment Preview:
(1:115) Warning: unescaped & which should be written as &
(1:136) Warning: unescaped & or unknown entity "&feature"







Go to the home page.

The & sign serves special purposes in HTML coding. If you paste a link that has one in it or use it by its self it will be invalid HTML. Naturally we just intend what we type here to be text and not HTML code. Just another little bug for Mr Caedes to get the system to ignore it completely.

To see what I mean look at this.

The warning "Warning: unescaped & which should be written as &"
(I think) should read-
"Warning: unescaped & which should be written as &amp;"

As for the flame in brackets, it is mistaken as an invalid HTML tag and discarded.
Another item that will have to be specifically ignored by the system.
Or you could do this...
*<flame> **</flame>
which is actually *&lt;flame&gt; **&lt;/flame&gt;

OK, my head hurts now... ¿

*ouch* David! My head hurts now as well and all I did was read the ^ comment :=)

David, if I may, could you repeat that part after 'The..' ... in an altogether and totally different way, so that I can understand?


Thanks, 'preciate it.

:oP

No, I'm not going back there! You can't make me!

I have suppressed the warnings about the & character, so you won't have to worry about those. Getting the flame fractal code to print out is going to be more difficult. Technically, you are supposed to use &lt; and &gt; in place of the < and > characters. I may be able to come up with an easier way for you to do it though.

Thanks very much, *caedes.

Will give the workaround a go, till a more permanent solution is in place. :o)