Have Business acct in pb v1; can we upgrade that instead of testing v2 with a free acct?
We have a paid business account in v1. We received a golden ticket for v2, and I mindlessly followed it and signed up, thinking I would be upgrading our existing account. Instead I find we have a v2 free account. Blah, how useless is this? The features we care about in v2 are apparently not available in the free version (folders, folder-level permissions), plus our AuthAPI integration must be redone.
Is it "suicidal" to upgrade a live (if rather new) wiki to v2? If not, can we do that?
Our live v1 acct is celearning, the v2 useless acct is cecredit.
Thanks!
Is it "suicidal" to upgrade a live (if rather new) wiki to v2? If not, can we do that?
Our live v1 acct is celearning, the v2 useless acct is cecredit.
Thanks!
1
person has 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.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The folders and security features ARE live in 2.0, are you having trouble with them?
Also, once we release 2.0 formally, we'll probably send out an email to all 1.0 wiki owners so you have the option of transitioning your wiki to 2.0, but we don't want to do this until we're sure there won't be any bugs. See this thread (http://getsatisfaction.com/pbwiki/top...) for at least one very good reason why this is so. -
Inappropriate?Hm, odd! When I played around the first time, I did not see a way to create a folder, but now I do. Alas, I cannot reproduce that situation and it may have been pure hallucination (as users often experience).
However, it *would* be a more realistic beta test if we were using the wiki as the real thing, and not just kicking the tires a bit with a test wiki.
I guess the only way to do that presently is to copy-paste/ all pages and re-upload files? -
Inappropriate?Unfortunately manual copying is the only way right now.
As for switching up, we'll be doing that soon, but that's not available yet. -
Inappropriate?Max,
We're still working on allowing people to upgrade 1.0 wikis to 2.0. I can tell you that we've already done so for our own corporate wiki without any real hitches. We will be making this available to our customers soon. For now though, please keep playing with your 2.0 account. -
Inappropriate?I have a 1.0 wiki that is not very active anymore. If you could ensure that the original content would still be there (e.g. through a backup of the current situation), it would be perfect to transfer that to a 2.0 and play around with it, without risking drama if it goes wrong. The wiki is not used anymore, so all changes I make will be for testing and hold no business risk...
In other words, I can re-structure and update a populated wiki without much worries that I would lose a lot when I encounter bugs. If problems arise, I'll be able to reset the backup. If all goes well, I will have just moved the wiki to 2.0.
-
Inappropriate?I've written a c# library that can use both the v1 api and the v2 api, so it would be pretty trivial to write a script that copies a 1.0 wiki to a 2.0 wiki automatically..... if the 2.0 wiki api had a method for posting data.
-
Just to make something? Yes, we already have that. To make sure that all the wild and wacky things users have done with their 1.0 wikis don't die a flaming death when they are introduced to 2.0? Slightly more difficult. But don't worry, we're on it :) -
Well, I think Tim's referring to creating such a script on his end, which, if you are using the API, would indeed be trivial.
For the POST...maybe you could make curl pretend to be you? May be easier just to wait for the proper function in the 2.0 api...
Loading Profile...





EMPLOYEE
