There is no reason to downgrade a working 2.2 site. It is a supported version, and there will be an upgrade path to the next version.

Rowd

Quote:

One thing I should mention is that it's not an official XOOPS project. It's my personal project, for the XOOPS community. So Brian and James would probably know very little about it.

And as Skalpa said in his post, he wanted official recognition of the project, but didn't get it. I just wanted it done, so people can start using it.

Rowd

I'm using phppp's port of DokuWiki for the workspace/wiki part of the site, with a few modifications. The modifications are for language support (each page can have a version in any installed site language), and page templates (certain pages when newly created will be prefilled with text based on a template - like a new module details page, or module user guide for example).

The site is not actually just a wiki, there's more which you'll see soon enough. The main thing to remember about the wiki though is that it's a workspace, a place for the community to collaborate on writing documents. When finished, a doc will be made into DocBook XML sources, and an HTML version generated and placed online as a release candidate for the community to comment on. Once approved, it can be released as a final document which is viewable online or downloadable in different formats. So the actual wiki part is more of a temporary workspace, it's not intended to store the documents permanently.

That said, there is another role of the wiki, and that's to help translators. When a doc is released as final, the workspace version will be locked so no editing can be done. Then translators can create a page based on the locked page, with the text and layout brought into their new page, and hopefully this can help them to be able to collaboratively work on translations. I've just set up the initial structures, it will need involvement and feedback from people using these tools to know if it's really workable, and what needs to be changed.

So for security of the wiki section, well... certain pages will be locked, such as final docs and site info pages. The rest will be open to any registered user. It will be up to the community itself to check for abuse of the workspace, and to restore previous versions of pages if the current one had been abused. Deliberate abuse of the wiki will result in the user being banned. It's a serious issue if users deliberately destroy the work of others, so it should have serious consequences. There will also be regular backups made of course.

This is how it will be initially setup. Changes are always possible though, if discussions determine them necessary. There is a forum for every available site language too, so people can have discussions about documentation in their own native language. The goal is to make collaboration possible, not just within the English community but within the entire XOOPS community.

Rowd

Thankyou Bender, I hesitated about posting in the other thread, but the posts went in that direction and seemed to require a response.

Thanks for getting the original thread back on track

Rowd

It's due to the installer not being fully compatible with PHP5. It will be fixed in the next release.

In the meantime, this post will help.

Another possibility... Do you use a right to left language, perhaps? and that's why you need the pages RTL?

If that's the case, try the XOOPS Persian dev site. They have released a theme which includes a css file for RTL positioning.

There's only a problem with the installer.

The fix has been posted many times, use the search function... or see this post

If you had tried searching the forum for 'Failed writing constant' you would have found a possible solution

Very cool

Nice work!

Skalpa has already committed a huge amount of code, I don't understand why people are still complaining that there are no changes... I can't believe they've actually looked.
I didn't have the luxury of a guided tour which the french team had, and I haven't seen what they've seen, but just looking at and working with what *is* available tells me enough.

Some of the enhancements I've seen and used:
- Completely new theming engine - templates are no longer stored in the database, but read from file (cache). The system first checks if a module template exists in your theme directory, if it doesn't then it uses the default module template. This means there's no need to update modules, upload template files or edit templates online to make the changes display, as long as the site is in development mode.

- Smarty template engine optimised -> Skalpa made changes to Smarty itself to make it faster. He's passed the changes on to the Smarty dev team.

- New default theme, standards compliant and illustrating how to use the new templating features.

- a number of core components have been modulised... for devs this is exciting, as it's cleaner and easier to work with and will ultimately make community code contribution easier... but for end users I guess there's not much obvious benefit yet.

- write-enabled directories are able to be located outside web-accessable directory.

- PHP notices about references should all have been removed finally (a huge task in itself, dozens (hundreds?) of lines of code needed to be 'fixed')

- a brand new admin plugin system. I've only seen part of this code, but I've seen screenshots of it in action and it's very impressive.

- Boot sequence optimized, only loading what's necessary - making page load times faster.

- preparing for PDO support (i.e. soon will be able to use databases other than mysql)

- backwards compatibility is maintained for every new feature

All new features are documented. Skalpa has also spent a lot of time designing a new phpDocs API template, and enhancing the in-file documentation so that generated phpDocs are much more useful to developers than what we currently have.

@ maxpt
Development definitely IS organised. The lack of news on the dev site doesn't reflect the professional way core development is now handled.

As for your point about regular updates to the dev blog I fully agree with you. I know it was Skalpa's intention to regularly post about what he's working on, I don't know why he hasn't. But I agree, a few lines each week, maybe a screenshot or two, would be wonderful.