Loading Profile...
Migrating from PBwiki 1.0 to 2.0
Hey Everyone!
We've been working hard on adding new features to PBwiki 2.0, including Classroom Accounts (which replace invite keys), reader comments, folders, easier editing, full CSS customization, and tons more. PBwiki 2.0 now allows you to do just about everything you could with PBwiki 1.0.
We're encouraging everyone to migrate to PBwiki 2.0. This helps us develop features in a simple, unified way, which means more features for you.
You won't have to do anything right away, but we recommend that you start taking a look at 2.0.
The details: You can migrate to PBwiki 2.0 today by clicking the "Convert Now" flag at the top of your wiki (the migration process explains how this works). Over the next few months, you'll get additional notices by email, letting you know what's going to happen. Then in March 2009, all PBwiki 1.0 wikis will need to migrate to PBwiki 2.0.
Again, you'll have plenty of time to migrate your wikis, and our Support and Services team can help you with any questions. Millions of people are using PBwiki 2.0 and are thrilled with the new features available to them. If you have any questions, please click "Help" in the top-right corner of your wiki.
We've been working hard on adding new features to PBwiki 2.0, including Classroom Accounts (which replace invite keys), reader comments, folders, easier editing, full CSS customization, and tons more. PBwiki 2.0 now allows you to do just about everything you could with PBwiki 1.0.
We're encouraging everyone to migrate to PBwiki 2.0. This helps us develop features in a simple, unified way, which means more features for you.
You won't have to do anything right away, but we recommend that you start taking a look at 2.0.
The details: You can migrate to PBwiki 2.0 today by clicking the "Convert Now" flag at the top of your wiki (the migration process explains how this works). Over the next few months, you'll get additional notices by email, letting you know what's going to happen. Then in March 2009, all PBwiki 1.0 wikis will need to migrate to PBwiki 2.0.
Again, you'll have plenty of time to migrate your wikis, and our Support and Services team can help you with any questions. Millions of people are using PBwiki 2.0 and are thrilled with the new features available to them. If you have any questions, please click "Help" in the top-right corner of your wiki.
I’m excited!
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hello Rachel,
I received notification of this in an email titled 'Introducing new features plus a complimentary upgrade'. I must say, I find the use of the word 'complimentary' to be disingenuous as it is being used to disguise that fact that all users of PBWiki will have to upgrade whether they like it or not. When a waiter brings around a complimentary glass of wine, I do not have to drink it, but I will be expected to upgrade in March despite my reticence to do so. Whilst it will not cost me money to upgrade, the word 'complimentary' also has connotations of a show of goodwill. I'm not sure that is the case here.
I have been using PBWiki for years now and have been extremely happy with its interface. Not all wikis take the form of project management portals. My wiki does not require the new features being touted and so I do not believe it is in my best interests to upgrade, losing the functionality and aesthetic I currently have in PBWiki 1.0.
This is not intended as an attack on PBWiki as I have been generally pleased with the support I have received from your company, especially in the early days. The two versions of PBWiki currently coexist happily. I just hope PBWiki can appreciate the impact a mandatory upgrade will have on a (small) percentage of its users.
Regards, Paul1 Comment
Add a comment
This is one of the best points
-
Hi Paul - I'd love to hear more about how you use PBwiki 1.0 and why 2.0 won't work for your specific wiki. Can you drop me a line at migration-help(at)pbwiki(dot)com? Looking forward to getting your feedback! -
Inappropriate?This message of Rachel is totally contradictory with Paul Singhs message found here:
"we won't force you to change if you don't want to"
and
"we won't cut off your 1.0 wikis and we don't plan to - ever".
Whazzup PBwiki? -
Inappropriate?Hello All:
Actually 1.0 and 2.0 have lived side-by-side for about 9 months. In those 9 months, our entire team has worked to make 2.0 a solution that more than serves the needs of our customer base. We have spoken to thousands of customers to get their feedback and input to make sure we made 2.0 a wonderful solution. And for the last 3 months we have been able to get 2.0 where it needs to be for our customer base.
Now to make PBwiki even greater we need to stop supporting our older and less viable solution (1.0). So by the end of February, 2.0 will be the only version of PBwiki.
1.0 has not been updated in any way in almost a year and retiring it is the right course of action. In the same time period 2.0 has added amazing features like:
Classroom Accounts
Unlimited Diskspace for Business Customers
Document Management
Custom CSS & Javascript Controls
And this is just the tip of the iceberg of what is coming in 2009.
Our amazing support and services team will hand-hold any 1.0 existing user over to 2.0.
TK1 Comment Add a comment
This is one of the best points
-
Thanks for clarifying, TK.
-
Inappropriate?I like 2.0 a lot, except for the new security settings.
It makes it really difficult because I want to
a) give a large number of people access
b) not make it public
c) not send invites to people unsolicited
d) let them have access right away without waiting for me to authenticate them.
With the old password method, this was really easy to do. Also, I miss the old sidebar that was always at the very top of the page.
I’m frustrated
1 Comment Add a comment
This is one of the best points
-
Hi Avocado, thanks for sharing your concerns.
a) Have you tried the publicly editable feature, that lets anyone with a PBwiki Account edit your wiki? The request access feature also is a great time saver for large groups of people.
b) Keeping your wiki private is very easy. Just go to "Settings" and then "Wiki Security." If you want your wiki to be private, just select the "Only people I invite" option for "who can view this wiki"
c) We do not send invitations to your wiki unless you have specifically typed in that email address and sent them an email. If you don't want to send invites at all, just send people your wiki URL and have them request access to the wiki. They can then decide if they want to join or not.
d) By choosing "Anyone with an account" for "Who can edit this wiki" on the Wiki Security page, your users can have access right away, without you needed to authenticate them.
I hope this helps! Please let me know if you have any other questions! -
Inappropriate?Well, it's more that I want to do all these things at once. So I can't have it publicly editable and also private, or have immediate access without sending invites, right?1 Comment Add a comment
This is one of the best points
-
The closest thing you can do is have a private wiki with request access- still requires you to approve, but it's pretty fast and easy.
Do you mind sharing how you're planning on using PBwiki? I'd be interesting in learning more about why you want to set up sharing in this way. -
Inappropriate?Avocado,
One of the big problems with your plan in 1.0 is that if you ever wanted to later deny access to someone to your semi-public wiki, you would have to change the password and notify every single person of the new password. Under the vastly improved 2.0 system, you just remove one user and everyone keeps going as they were. -
Inappropriate?I work for a library system, and the wiki is for one of our committees. There are several hundred people who might conceivably want to look at the wiki, but realistically maybe only a few dozen might actually look at it.
To address TK's point, I don't have any reason to revoke access--it's not like there's anything super secret on there, but I'd just as soon not have the whole web be able to see it.
I think it'll have to be the "request access" way, but we have a lot of people who aren't very web-savvy and this just makes it a lot more complicated for them. Also people don't always like having to sign up for something. A simple password would be a lot easier.
I’m resigned to making do...
1 Comment Add a comment
This is one of the best points
-
I'm a librarian too, so thanks for sharing your use case.
If individual identity is not important, you could just create one generic PBwiki Account and have all your users log in with that info.
If you're using an educational wiki, and don't want your users to have to sign up, be invited, or approve them, you could create classroom accounts for your users and hand them out. More information about classroom accounts can be found here: http://pbwikimanual.pbwiki.com/My%2BP... -
-
Inappropriate?So if I create one generic pbWiki Account can all my users use that account to get access to my pbWiki at the same time?1 Comment Add a comment
This is one of the best points
-
Hi Aga, you could do that, but then you lose the security of having individual users identified, and the ability to track revisions. Is there a reason why you don't want users to have their own PBwiki Accounts? Maybe we can come up with a better solution for you!
-
Inappropriate?We are using pbWiki to set up sign-up lists for parents to volunteer at our school. The single password system works very nice since I don't have to approve access for more than nine hundred parents. And it was quite a bit time to get parents to use pbWiki. If I now require them to create pbWiki Account a lot of them will just stop using. One of incentives how easy to use pbWiki was that it require them to remember just a password and they do not have to share their e-mail address.1 Comment Add a comment
This is one of the best points
-
Hi Aga,
Your solution (one PBwiki Account login) would probably work just fine. You could also create classroom accounts for each family to log in with (the classroom account procedure gives you a printout slip you could give to each family). -
Inappropriate?I will definitely consider using classroom accounts in future. And generally I like how pbWiki moves to more flexible and more controllable setup. It is just that I need move slowly in educating people how to use our sign-up lists. You wouldn't believe how many times parents said they couldn't figure how things work even though they do use e-mail and text editors. Takes time to make them comfortable to use new things...
-
Inappropriate?Hi,
I would be extremely pleased if you could add the Classic Editor Mode to the 2.0 PbWiki.
I am so far very happy with pbwiki, one reason being the easy editing in the text mode.
Adding a couple of links with the new editor is a real pain if you are used to text editing.
Any chance of that?
Thanks.
I’m a little frustrated
-
Inappropriate?Hi Ab,
I'm sorry, the Classic editor is gone for good. However, we may be introducing a feature that will give you back a few time-saving shortcuts that may help.
If you are interested in trying out that feature while it's being tested, please join our Alpha Team.
http://blog.pbwiki.com/2009/01/29/joi...
The feature is called pbautokeys.
Thanks for telling us what you like and don't like.
-
Inappropriate?well, the feature that I loved is that I can paste an url to a link as text without going thru dialog boxes.
But if thats not in PBwiki anymore, I tested TiddlyWiki the last days and that looks just as good for my purposes (few users, text mode editing). Sorry to leave pbwiki however.
-
Inappropriate?Hi Ab,
PBwiki does support the ability to simply paste a URL into a page and have it appear as a link. Have you had problems getting this to happen in a wiki?
I have used Tiddly Wiki myself. It is a great portable wiki, but if you need to share it with others online, you will find that it's very difficult to do so.
EMPLOYEE
