I've got a thread in new users & general questions. I worked up a longish reply to 3 posts. I tend to take so long composing a reply that my forum login times out... So I copy/paste the post()s I'm responding to into a text file and write my reply there. Then I come back to the forum and paste it into the compose editor... Then I use preview to make sure I didn't have ant typos in the embedded BBCode that manages quote and code boxes...
But All I'm getting there is: I even tried to preview a short mini- post with zero BBCode to see if maybe it was something in the text of my post that was giving the previewer fits. But it keeps insisting that I'm forbidden???

What the {expletive deleted} is happening?

/ etc with out the space is the cause. Or drop the / .

OK so I went back to my thread in general questions and started pasting in my message a few lines at a time and previewing each paste...

I found out that the forum post process didn't like a pasting of the terminal output of
even though it was in code tags...

I note that this posting wouldn't let me include the full pathname of default.target in the above code tag...

IE: (here substituting commas for the directory separator slash character):
What the heck does the forum software have against full pathnames??? (even when INSIDE code tags???)

Shay wrote:/ etc with out the space is the cause. Or drop the / .

Oh so it's just"/" +"etc" that causes this:

so then this should work:
I can live with that... But it just don't look right. {sigh}

Thanks for explaining it to me.

"doesn't look right"

Agree.
So, instead of inserting a space, you can straddle"a forward slash character immediately preceding etc"
with bold or italic or color square-bracket tags.

/etc
/etc
/etc

It's a 5yr old bug with the forums software, and freeforums leaves it in place... as an upsell motivation
(the bug is fixed in the version of phpBB forum software used in hosting the PAID forum instances)

test for the etc bug
/etc
edit
/etc

Had at least one extra brain wave today!
It just happened to occur to me that we could perhaps circumvent this age old bug by adding"/etc" as a"bad word" /"censored word" that is simply replaced with itself rather than *****.

Seems to have worked for me if anyone else would like to give it a go.

/etc does in fact work, but subfolders do not (/ etc/wellwhatdoyouknow for instance).

Hmm bummer.
Cheap thrill __{{emoticon}}__

So If I understood then this should work:

Maybe I should have said: wrote:

Code: Select all

JtWdyP -> /mnt[b]/[/b]etc
> ls -l [i]/[/i]etc/systemd/system/default.target
lrwxrwxrwx 1 root root 41 Jun 10 21:34 /[u]etc/systemd/system/default.target[/u] -> /usr/lib/systemd/system/multi-user.target
JtWdyP -> /mnt[i]/[/i]etc
> 

JtWdyP -> /mnt/etc
> ls -l /etc/systemd/system/default.target
lrwxrwxrwx 1 root root 41 Jun 10 21:34 /etc/systemd/system/default.target -> /usr/lib/systemd/system/multi-user.target
JtWdyP -> /mnt/etc
>

The good part of this, is that by pasting that kind of encoding outside of any"code" tags the displayed text can be copied and pasted into a text editor such as leafpad, kwrite, or my personal favorite, vim and the pre-BBCode, code of some valid command line example. Something that contained"/etc" could be executed. Say something like this:

[code]
cat /etc/group |grep wheel
[/code]

Which could also, of course, be pasted directly into a command line...

In my case the problem shouldn't be in the ability to circumvent this /etc bug, no my problem will be in remembering that I might need to... {sigh}