Hi Deryk,
I believe I have fixed this but I will perform some proper checks over the course of this week (feel free to nag me if I don’t get back to you).
I noticed that you posted an intention to work on a ‘group pages’ plugin. Any progress with this? It sounds like it could be a nice replacement for bp-wiki.
I’ll check out your plugin again. The only reason I would write the plugin I described was because of the fatal flaws in previous versions of your plugin. I’d rather not re-invent the wheel if your plugin is now working properly. A wiki plugin that loses data is a pretty serious bug, that is why I stopped all work on your plugin. It would be great to know definitively if this is fixed or not. thanks 🙂
Just to update you – blockquoting seems to be okay, though I need to add a css rule (feel free to suggest one if you have a preference).
Style tags don’t lose content though they get converted to html commenting tags… Obviously this isn’t optimal as the content within the style tag is then only viewable in edit>html view. I’ll look into sorting this shortly.
hey David, thanks for the reply. I think less is more at this point. fewer features and very stable. I noticed a bug that when you are editing a post you cannot edit the title. why not remove the ajax from title editing, and just make it editable when you edit the post – like wordpress does with posts.
Boone and I need a plugin that offers similar functionality as yours and we made some suggestions about your plugin here https://github.com/boonebgorges/bp-wiki/issues. In the end it might be easier for us to code something from scratch.
take care,
Deryk
a really nice fix would be to set the default privacy of wiki pages based on the group setting. A private group should default to having a private blog. This has confused users.
Another coding suggestion: don’t have a separate function for edit and create. That is the golden rule of code modularity and will save you so much headache in the future.
