Supposedly I should be unable to post the following according to a bug report:
<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

No, here it works. It doesn't work in the Seti forums.

It doesn't work in PM either... let me PM it to you. :-)

---

No, here it works. It doesn't work in the Seti forums.

It doesn't work in PM either... let me PM it to you. :-)

No, it's OK in every forum I've seen - if anything, we have too many of them at SETI (heavy use/quoting of app_info.xml).

It's the PM system which is broken, here and at SETI.

Alright, I've been able to reproduce this on my test project. Looking into it. Does this have a trac ticket?

---

Something eats BBCode tags as well on the Seti forums, when putting it in code or pre tags. Let me test here.

[img]http://link_to_elsewhere.jpeg[/img]

[img]http://link_to_elsewhere.jpeg[/img]

Preview shows the above as nothing being there.
Posting shows the "broken" image link... it shouldn't activate the code in any way. not in the code tags.

---

Something eats BBCode tags as well on the Seti forums, when putting it in code or pre tags. Let me test here

That's a seperate issue.

---

Something eats BBCode tags as well on the Seti forums, when putting it in code or pre tags. Let me test here

That's a seperate issue.

Agreed, just flagging it. ;)

You saw what I meant in the PM, though.

---

Update: Found an issue in inc/pm.inc:pm_send() : A call to striptags() on the content text.
This is most likely a bug - but fixing it requires checking whether any other part of the code relied on the tags being stripped already there. So this may take a little while to fix.

---

testing the other thing.

<tag_it>

Editing post... No, here it still works after edits.

---

Fixed the first issue you described, the change should eventually end up here.

---

Thanks for the quick fix, Janus.

---

And thanks from me too.

What's the best way of alerting/requesting SETI to apply the new code? That's where we really need it. (And probably SETI Beta too, though they usually do them in tandem).

And while we're all here: this fancy new coloured background that Jord has had for a few weeks. I suppose it's triggered by one, other or both of his status tags. Useful: I can see it picking out Moderator or Project Scientist posts in a discussion thread.

But it doesn't work very well at SETI Beta, where everybody, without exception, is given a <Volunteer tester> tag. Is there any way the background could be made a bit more selective?

Email or PM Eric Korpela or Matt Lebowski. That they change it during the maintenance outage tomorrow.

---

And while we're all here: this fancy new coloured background that Jord has had for a few weeks. I suppose it's triggered by one, other or both of his status tags. Useful: I can see it picking out Moderator or Project Scientist posts in a discussion thread.

Go to your account, forum preferences, uncheck Highlight special users and save changes.

Or ask Eric to exclude the role of <volunteer tester> from these highlights.

---

And while we're all here: this fancy new coloured background that Jord has had for a few weeks. I suppose it's triggered by one, other or both of his status tags. Useful: I can see it picking out Moderator or Project Scientist posts in a discussion thread.

Go to your account, forum preferences, uncheck Highlight special users and save changes.

Or ask Eric to exclude the role of <volunteer tester> from these highlights.

It's really not worth pestering him - there are other things I would much prefer he spent his time on.

Hadn't seen the 'Highlight special users' option before (don't often visit those pages). Strange thing is, the preference is present and checked in my SETI Main account, but there is no highlighting on the SETI Main forums: must be in some sort of half-updated state.

Do you think if I can get Matt or Eric to update the code for the PM-bugfix tomorrow, I'll become a 'special user' too, along with all the other volunteer testers? (who are also automatically tagged at main, if their accounts can be linked up)

Do you think if I can get Matt or Eric to update the code for the PM-bugfix tomorrow, I'll become a 'special user' too, along with all the other volunteer testers? (who are also automatically tagged at main, if their accounts can be linked up)

Aren't you special already? (Annoying, irritating, etc. etc. ;-))

They don't do special roles on the forums there, but for the volunteer tester and volunteer developers roles. The latter should be given by the admin, the former is given when you attach to Beta with the same email address as used on Seti main.

I've only managed to get rid of mine by changing the email address on Beta to something else.

---

Email or PM Eric Korpela or Matt Lebowski. That they change it during the maintenance outage tomorrow.

Done.

Do you think if I can get Matt or Eric to update the code for the PM-bugfix tomorrow, I'll become a 'special user' too, along with all the other volunteer testers? (who are also automatically tagged at main, if their accounts can be linked up)

Aren't you special already? (Annoying, irritating, etc. etc. ;-))

And frequently blue in the face, if not in the background.

Fixed the other issue as well with the exception that it only works for CODE blocks - not PRE blocks.
The reason is that CODE blocks use divs with stylesheets allowing us to use escaping of [ to break out of the BBCode parsing. Pre tags are implemented directly as HTML pre tags and hence do not allow escaping (the escape code would show up instead of the actual char).

The solution is of course to make PRE blocks do the same thing as CODE blocks do now:
1) Add a style for pre divs and convince all projects to update their CSS
2) Make 'pre's do what 'code's do now in text_transform.php

I left that as an excersize for the reader.