When you edit the TWikiAdminGroup
topic - and that we must assume the newbie admin does with normal Edit (ie. TMCE) then the yellow table which is HTML mixed by TML bullets - is turned into TML table with HTML bullets. And the yellow background is lost.
Can we protect an area against being altered?
Can we at least for this topic create a yellow area which is not destroyed by TMCE?
The configure help text refers to a yellow text so we need to fix something here. Even if it is just changing the doc to a TMCE safe version.
- 17 Sep 2007
This alternative survives
| How add the first Administrator:
- To add yourself as the member of the admin group you must be registered as a normal user
- Next you must Log In as this normal user
- Authenticate as the internal TWiki administrator using the internal admin login (use the username already suggested and use the password set in configure).
- You can now edit this topic
- Insert wanted users in the TWiki Administrator Group by listing them in the GROUP setting
* Set GROUP = JohnSmith, JamesBond)
- Save this topic
- Verify that new members show up properly in the group listing at TWikiGroups
- Make sure always to keep this topic write protected by keeping the already defined ALLOWTOPICCHANGE setting
- The ALLOWTOPICHANGE and ALLOWTOPICRENAME settings in TWiki.TWikiPreferences and Main.TWikiPreferences have already been set to this group (TWikiAdminGroup), restricting edit of site-wide preferences to the TWiki Administrator Group
- 17 Sep 2007
I could just check this in but I will sleep on it. Maybe there is a better way.
We need a feature to protect an area against TMCE. The PROTECT style is temporary. Maybe we need a <protect> type of tag.
- 17 Sep 2007
I really, really, really don't think that's a good idea. We don't want to encourage people to embed uneditable text into the middle of topics. Either make the whole topic raw-edit-only, or accept that the WYSIWYG version of the same thing will be slightly different.
Reattributing to Documentation
Having said that I just read Item4678
. It seems that you are not the only one.
The obvious thing to do is to add a class to any HTML element that you don't want touched by HTML2TML
. For example:
this would prevent HTML2TML
working on that tag or any tag within it
, which addresses Sven's requirement but not Kenneths.
You can surround key HTML sections with <literal> tags and thereby not only protect them from TML, but edit them in WYSIWYG using the HTML editing features. Apply the LITERAL style in the editor.
Mixing TML and HTML and selectively protecting the HTML from conversion is just too complex IMHO.
Checked into MAIN but NOT
into TWikiRelease04x02, in anticipation of feedback.
I think its important to have a way
and for the docco for it to be obvious from raw-edit .
I somehow thought the tinymce 'PROTECTED' sectino would do it, but with my problems using safari, i never got around to finding out what 'PROTECTED' did, or howto use it from raw-edit (somehow i thought it would be a persistent style)
- 21 Sep 2007
The difference is subtle.
PROTECTED lets you edit raw HTML (in the editor you see HTML, not the rendered result), but once you have entered it is saved as inline HTML. LITERAL on the other hand lets you edit the presentation (you see the rendered result in the editor, not the raw HTML) but when it saves, it wraps it in <literal> tags. So, if I type <big>crocodile</big> twice in the raw editor, once in <verbatim> and once in <literal>, I get:
When you WYSIWYG edit, you see the same thing.
Now I will WYSIWYG edit, type <big>crocodile</big> again, select it and choose PROTECTED style:
You can see that it has saved the literal HTML inline, but has not
put literal tags around it. So the PROTECTED style is transitory only
- it protects your typing for as long as it takes to save the topic once
but it doesn't stick. This is unfortunately needed for when you want to type raw HTML into the browser and have it saved exactly
as you typed it, but not
in literal tags - for example, when entering a Set value, or when entering HTML that will be completed when a TWiki variable is expanded (and is therefore invalid HTML in the editor).
Basically PROTECTED style will only ever be used by people editing TML concepts such as TWiki variables and Set statements. LITERAL will be used by anyone else who wants to embed literal, protected HTML in their topics.
- 21 Sep 2007
Changed from Documentation to TMCE, since this has developed into a coded feature.
That said - I do not quite understand what is happening here
PROTECTED is a style which is not really a style.
LITERAL is added but I cannot see it in UI of TMCE.
If I type literal tags and put them round some HTML I want to protect then it works if I save in Edit Raw.
But if I then open the same topic again and save it, the newline in front of literal is removed.
Each time you save another newline in front of literal and /literal are removed and soon the topic format is gone.
I will open bug items for these.
Once the literal feature is working - I know how to make the TWikiAdminUser
yellow text robust and still easy to edit again.
merged and closed
If the summary of this bug is still descriptive, the bug is open again - the table is still altered.
Possible workaround: Put the admin-doc/note in a "HowToMaintainTWikiAdminGroup"-topic and include it instead of maintaining the yellow table in the topic itself?
- 21 Oct 2007
I actually planned to do it with LITERAL
But when I saw CC closed the bug I never followed up on it because I assumed CC had fixed it.
- 21 Oct 2007
You can use <literal>, as I did when I fixed it (how did it get broken again?), or you can put <sticky> tags around it.
- 24 Oct 2007
I'll fix it again
I cannot use literal. See Item4888
- 25 Oct 2007
Sticky worked. Sticky it is. I also moved the settings back to the top. Otherwise the new admin will have to search for the setting among the blabla.
Cleaned "WaitingFor" field.
- 10 Aug 2008