( ! ) Warning: session_start(): open(/var/lib/php/session/sess_lg85ht4d7so9trhfh943p2k8p7, O_RDWR) failed: No such file or directory (2) in /var/www/bitweaver/live/users/includes/bit_setup_inc.php on line 82
Call Stack
#TimeMemoryFunctionLocation
10.0000232176{main}( ).../page_history.php:0
20.0001234232require_once( '/var/www/bitweaver/live/kernel/includes/setup_inc.php' ).../page_history.php:16
30.02251908296BitSystem->scanPackages( ).../setup_inc.php:141
40.02452176576BitSystem->loadPackage( ).../BitSystem.php:1183
50.02452179608include_once( '/var/www/bitweaver/live/users/includes/bit_setup_inc.php' ).../BitSystem.php:1109
60.02492583856session_start ( ).../bit_setup_inc.php:82

( ! ) Warning: session_write_close(): open(/var/lib/php/session/sess_lg85ht4d7so9trhfh943p2k8p7, O_RDWR) failed: No such file or directory (2) in /var/www/bitweaver/live/kernel/includes/classes/BitSystem.php on line 580
Call Stack
#TimeMemoryFunctionLocation
10.0000232176{main}( ).../page_history.php:0
20.05615012232BitSystem->display( ).../page_history.php:57
30.05655014200BitSystem->preDisplay( ).../BitSystem.php:505
40.05795028968session_write_close ( ).../BitSystem.php:580

( ! ) Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in /var/www/bitweaver/live/kernel/includes/classes/BitSystem.php on line 580
Call Stack
#TimeMemoryFunctionLocation
10.0000232176{main}( ).../page_history.php:0
20.05615012232BitSystem->display( ).../page_history.php:57
30.05655014200BitSystem->preDisplay( ).../BitSystem.php:505
40.05795028968session_write_close ( ).../BitSystem.php:580
- bitweaver

Version 2

Top 10 things to do immediately after installing Bitweaver

Created by: xing, Last modification: 25 Oct 2008 (08:36 UTC) by xing

Not tweaking performance and security

Bitweaver ships with good defaults. The install is safe, HTML input is disabled, several caches are enabled, and so on. Still, to get the most out of Bitweaver, you'll have to follow all the docs there are on performance and on security to optimize your site.

Enabling every package

If your site gets one gazillion clicks a day, you need a forum and a blog for sure. Until then ... do your users really want to tag, comment, vote, recommend, have their own blog, post to the forum, message each other, subscribe to your newsletter, upload their podcasts and videos, post and share images, and save their wiki pages as PDF files? It's a good idea to focus on one thing. If that thing is a "social web platform", well, in that case you probably do need all packages. If you are looking to setup Bitweaver as a personal blog, it might be better to install that package first, and enable other packages as you go along. Packages don't have to be 100% available to the public. In a blog, you'll still want to post pictures or podcasts, and use Fisheye and Treasury to collect and manage them. Yet the existence of these package does not have to be known to your readers beyhond their ability to look or listen or vote (or recommend, and so on). Lining up extended functionality behind one major hook can be a great way to channel the attention of your visitors.

Not reading the docs

Occasionally, Bitweaver claims that it's easy to use. If you look at it closely though, well, it is easy, but not easier. The approach to keep it modular and extensible has some great advantages, but for somebody not familiar with documentation, it's hard harvest those advantages. By some, Joomla is considered a CMS that's easy and intuitive to use. If you go through Joomla's admin panel, you'll find a slick click'n'go interface with a great many of options. After a while of learning, one understands how to do things "the Joomla way", so to speak. For something like this, Bitweaver is not quite the right choice. While there is a "Bitweaver way" of sorts, once a Bitweaver install is transformed to the website of your liking, it might not be that similiar to other installs anymore. Packages can do (almost) all they want, which means that your package can do what it wants. By configuring your Bitweaver to your liking, you might find yourself drifting away from an initial "Bitweaver way". The other way around, where an admin installs a CMS and has to push his content and concepts towards the CMS, is what Bitweaver is trying to avoid. Another example might be Plone. This CMS is also very powerful. Its content packages provide very similar same interfaces. When you use Plone as your CMS and upload an image to your site, it looks and feels very similar to editing a comment or sending a newsletter. With Bitweaver, eventhough it is the case more often than not, you can't be certain that using package X is similiar to using package Y, and your extension is not forced to be similiar to anything.

Using the default styles

The default styles (aka themes) are superbly written, but they look poor and have no personality. They say nothing about anything, because they are supposed to show everything to everybody. Use them only if your site is supposed to bet that person. At the time of this writing, there are hardly any specialized styles available. You should come up with your own. It's very easy to style Bitweaver, you'll be surprised. It's also very easy to take an existing layout from one of the many open source web design sites, and transform it into a Bitweaver style. It's merely a task of pushing some DIVs around and renaming some classes. When you are finished, you can upload your style to join (start) the Hall Of Fame.

Not visiting #bitweaver

The IRC chat channel Live Support is where the action is. To get answers or to follow the delevopment of the code, hang out in that channel for a while. It's not a chit-chat channel (except sometimes). It's a place where developers, users, and reporting bots communicate with each other.

Mistaking community for monolithic

Bitweaver's developers are a group of different people with different ideas. Some documentational pages are worded along the lines of "we are trying to provide you with a great product" and such. While this is true, Bitweaver is not a company, there's no support other than people trying to help you, and no code other than people feel like writing. There's a touch of "do and let do" in the Bitweaver community, and so it is a diverse one.

Not contributing

Seriously, Bitweaver is not a commercial product. While much code moves forward because of special needs of developers using Bitweaver to make a living, there are tons only being moved to accommodate guys like you and me. It's really great if somebody not only points out a bug, but also submits it to the bug tracker! Of course, investigating beforehand if it's already been submitted (or fixed). There is also lots of room for improvement of the wiki pages of the online documentation, such as the one you just read. ;)
Page History
Date/CommentUserIPVersion
31 May 2010 (10:30 UTC)
Added the way to remove packages.
Tochinet193.191.209.2447
Current • Source
laetzer85.178.0.1706
View • Compare • Difference • Source
Will69.203.72.1615
View • Compare • Difference • Source
laetzer85.178.46.1504
View • Compare • Difference • Source
laetzer85.178.46.1503
View • Compare • Difference • Source
xing62.47.238.2452
View • Compare • Difference • Source
laetzer85.178.0.71
View • Compare • Difference • Source