Loading Profile...
script support in 2.0 and upgrade mandatory?
I have a private 1.0 PBwiki (with over 150 pages) where I use some javascript and a test with
https://forumdemo.pbwiki.com/FrontPage
tells me that non of my code works in 2.0 anymore.
That's a big problem, the html and javascript support was the main reason I've chosen PBwiki!
I copied the core of my Sidebar code here, that you can see what I'm talking about:
http://testwk.pbwiki.com/FrontPage
So the Question is how I get something like that to work in 2.0?
I know there are Browsers which have such quick search features, but I have many different computers at home and work, with different browsers and don't want to configure them all when something changes.
I know the thread: http://getsatisfaction.com/pbwiki/top... but from the answers there I don't have much hope to see javascript in 2.0 soon.
My suggestions / questions to PBwiki:
1. Make a HUGE warning for everybody who even thinks about upgrading to 2.0 that during the "upgrade" all javascript is deleted and cannot be added back. Especially since you can't go back to 1.0 once you've upgraded.
2. Allow javascript in private wikis.
3. Allow javascript in Sidebar and make it editable admin only. or something similar.
4. How do I make sure that my 1.0 wiki does NOT get "upgrade" to 2.0?
5. Will javascript in 2.0 be available before we are forced to upgrade to 2.0, will there be an option to _never_ upgrade to 2.0 if you don't allow javascript for it?
https://forumdemo.pbwiki.com/FrontPage
tells me that non of my code works in 2.0 anymore.
That's a big problem, the html and javascript support was the main reason I've chosen PBwiki!
I copied the core of my Sidebar code here, that you can see what I'm talking about:
http://testwk.pbwiki.com/FrontPage
So the Question is how I get something like that to work in 2.0?
I know there are Browsers which have such quick search features, but I have many different computers at home and work, with different browsers and don't want to configure them all when something changes.
I know the thread: http://getsatisfaction.com/pbwiki/top... but from the answers there I don't have much hope to see javascript in 2.0 soon.
My suggestions / questions to PBwiki:
1. Make a HUGE warning for everybody who even thinks about upgrading to 2.0 that during the "upgrade" all javascript is deleted and cannot be added back. Especially since you can't go back to 1.0 once you've upgraded.
2. Allow javascript in private wikis.
3. Allow javascript in Sidebar and make it editable admin only. or something similar.
4. How do I make sure that my 1.0 wiki does NOT get "upgrade" to 2.0?
5. Will javascript in 2.0 be available before we are forced to upgrade to 2.0, will there be an option to _never_ upgrade to 2.0 if you don't allow javascript for it?
I’m sad
2 people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?"So the Question is how I get something like that to work in 2.0? "
Try placing your code inside a Google Gadget plugin. Currently that is the only place where they are not stripping JS.
Example here. -
Inappropriate?Javascript will be re-enabled as a premium feature once the security issues have been fixed.
Thank you for your patience.
1 Comment
Add a comment
This answers the question
-
Anyone at PBwiki care to share these "security concerns"? -
Inappropriate?I know the trick with the plugin, but if javascript is considered as a security risk, then it's also a security risk in a gadget, so it's only a matter of time, until it will get forbidden there also.
@Casey Greene: is that an official statement that javascript will never be available in a free 2.0?
When the security issues are fixed, what's the reason to not enable the feature for all wikis, since it is available in all free 1.0 wikis since quite some time.
Don't take me wrong, I know that your company needs some mony for providing this systems.
And I would instantly pay 10$ (I'm european, so it's cheap at the monent anyway ^^) for enabling javascript on my prvate wiki onetime.
But 100$ per year is a lot of money for just enabling javascript, since I don't need any of the other additional features.
PS: Whats with the other questions, upgrade to 2.0 mandatory at some point? When?
I’m sad
1 Comment Add a comment
This answers the question
-
As far as I have been informed, JavaScript will be a premium feature.
I think your question about upgrading to 2.0 has been answered already, I'll try to hunt down the thread :) -
Inappropriate?It's interesting... pbwiki is sort of straying from its initial vision... "easy as a peanutbutter sandwich" has been replaced by... "as secure as a peanutbutter sandwich"....
Err.. I guess the metaphore breaks down here, but perhaps that's telling.. given the number of threads that address this or very similar issues, it's pretty clear that pbWiki 2.0 is a second revision that really missed the point of what attracted so many people to pbWiki 1.0... perhaps that's intential because there is an awareness that there's a large unserved market that needs something exactly like pbWiki 2.0... but calling it pbWiki 2.0 and implying that it's what all the pbWiki 1.0 users are going to want and need is either spin, being out of touch, or just denial.
Hopefully pbWiki will find its way soon...1 Comment Add a comment
This answers the question
-
I think you raise a lot of really interesting points, Tim. Ultimately, I think we want PBwiki 2.0 to BE what users want, but I think we realistically know that it's not yet suited to every user's needs (people can still make 1.0 wikis, after all). I don't think security and ease are mutually exclusive and I think we're looking for ways to balance that.
