Loading Profile...
switching editor causes loss of manual HTML markup
I want to make certain (external) links open in a new browser window or tab. To do so, I switch from my usually-preferred WYSIWYG editor to the "classic" wiki-markup editor and code the links using a target="_blank" ... -- works fine. I go back to working on the page with WYSIWYG editor. But when I change editor to "classic" again, perhaps to add another external link, my original HTML markup gets lost -- perhaps because the WYSIWYG-to-classic translator doesn't differentiate between WYSIWYG-created links and those marked up differently/manually. This makes the effort of adding HTML markup futile & frustrating. Can this be fixed?
I’m frustrated
2 people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?If you had ever visited the old forums, you'd find dozens of threads that make one things very clear: NEVER switch between the two editors. It will destroy your formatting. As for whether it can be fixed: since they're still crowing about the "PBwiki 2.0" (to be released early this fall), my guess is that no changes will be made to the existing editor(s), since 2.0 supposedly has "new & improved" editing. Stay tuned to blog.pbwiki.com for when 2.0 becomes available. -
Inappropriate?You're right, Rupert, I would have found that flavor of warning if I'd been looking for it, rather than to resolve what looks an awful lot like a bug. I did try to find an answer to my question (but not to wholesale warnings about switching editors) in the forum before I posted, without success (did I fail to look hard enough? dunno...). I am new to pbWiki (but not to wikis in general -- I've used Confluence a fair bit), and I'd call this a fairly severe usability problem: there's something I can't do in the editor I like, I can do it in my "second choice" tool, but using the tools in alternation (essentially) corrupts my page. Can I work around this now that I know it's the way pbWiki works? Sure! But one of the attractions of pbWiki for my use is that future participants in my wiki will be put off by wiki-markup ... I need a workable WYSIWYG editor for their use. I'd like to see this solved, but perhaps pbWiki isn't what I'm looking for if I can't wait until early Fall. -
Inappropriate?Sorry. Yes, it is a well-known, long-standing bug. No, you cannot fix it. No, you cannot work around it.
According to the threads on the old forum, back when they introduced the WYSIWYG editor, users requested the ability to "lock out" the "other" editor, precisely to avoid this embarrassing bug. They chose not to do so. They do not consider this a problem.
I’m looking forward to some corporate-speak
-
Inappropriate?I don't know about corporate-speak, but it looks like there are two issues here, which I will try to address honestly:
1) Switching between WikiStyle and Point&Click: This is an acknowledged problem that Brian has spent a lot of time improving, but there are definite bugs in it. Chances are that this is something that won't be fixed, because PBwiki 2.0 uses the P&C Editor.
The solution for adding HTML in the P&C editor is to use the HTML plugin ("Insert Plugin" --> "PBwiki Magic" --> "HTML"), and that always works fine for short bits of HTML; of course you don't get to see links made this way as actual links while editing.
2) Having links open in new windows: This is a feature that has been asked for and one that the developers are aware of. Last I checked, it isn't in the 2.0 editor yet. I'm looking into it though, as it's a feature I would like as well. So that said, what can you do?
For now, you can use the raw HTML solution above, which will not change the formatting of your page. If you're feeling brave, you can actually switch to source mode in the P&C editor and add the proper code (I assume you're using something like "target=_blank") inside of the link tag manually.
Thanks for the feedback!
Vu
EMPLOYEE
