whissip - «b2evolution done right»

wassup?

Whissip is a derived branch from b2evolution, with additional features.

For example:

• Requires PHP5 and does not support PHP4 anymore (this is a good thing!).
• Uses UTF8 internally for encoding only; this allows to mix contents using different charsets on a single page and does not require input/output conversion.
  Also this allows such trivial things like using "totally abstract and not gainable" words/meanings like "爱" in your user name. b2evo itself totally barks out at that.
• DB class does not fetch all results and caches them in a PHP array; this results in better performance and less memory usage.
• Improved format for global.php (translations), using single quotes, and avoiding runtime conversion; this provides better performance.
• "Publish NOW" button considers "Protected" and "Private" as published, too. In particular, it does not set a post to "published", if it gets created as "protected".

I try to maintain a list of differences in doc/whissip_changes.txt.
The list of actual differences can be viewed at github: compare cvs-mirror to master.

where?

For now, you can get it from github. If you have Git installed, just do:

A demo is available on the b2evolution test/demo server.

You can download a tarball/archive via Github's export from https://github.com/whissip/whissip/tarball/master.

To install it, the following might work:

• cd $somewhere_you_want_to_put_this
• git clone git://github.com/whissip/whissip.git
• Make the whissip/blogs directory your webserver's document root
• Go to your document root in your browser (e.g. http://localhost/). Install.
• After installation, you may want to commit the settings:
  git commit -m "Add config"
• When you do any local hacks/changes to whissip/b2evo files, you can just commit them (to your local clone/branch).
• To get new upstream changes, do git pull. This pulls in upstream changes and will commit them to your local clone automatically, if there are no conflicts.

Please contact me in case of any discrepancies or suggestions.

future?

Do not ask for the future, live the present.

logo?

Currently, it still uses the derived b2evolution branding, but it may make sense at some point to use a separate logo.
Some submissions are already available.

bugs?

Please report any bugs and feature requests!

layout of this page?

Down here it's CSS Naked Day all night long.

Maintainer?

This branch/semi-project is maintained by Daniel.