Problem with wordpress

[anasporn]

Originally Posted by whitey

Got it installed as well as textpattern. Having significant ISP problems today - first in about 2 years - and am giving up in frustration for a couple of beers.

Hopefully, be able to PM you later or tomorrow with observations.

Cheers

Do it tomorrow LOL I can read typoese, but not drunkese

[whitey]

Originally Posted by anasporn

Do it tomorrow LOL I can read typoese, but not drunkese

Quick Review of Habari:

First off, my overall evaluation is that it is a fast, simple platform for publishing a blog. I think one would have to tweak it, as they do with Wordpress, to do a static site or a static site with a bit of dynamic content. It runs fast, uses few resources, has an intuitive interface and your page loads quickly (when I have my site ready, I will publish the url here).

That said, there are some issues to be aware of (are there not always issues with software and scripts). I would say this platform is about 95% ready for the adult blog market, out of the box so to speak.

The overall issue is that this is a platform written by true coders. As such, it is elegant and runs fast AND the docs are written for coders - meaning it takes some time to decipher the docs for a regular person. Once decipered, however, it is easy to install and run with the following warnings:

1. You need object oriented php modules installed in your server - .pdo and iconv. I run my own servers and they are configured as such, but most hosts will have to load these specifically at your request.

2. The install is easier if you have shell access.

3. As mentioned, the docs are a bit coderesse. As such, it takes time to figure out how to do something. Once figured out, it is always elegant, logical, easy and fast to use, but figuring it out is the issue. Right now, I am trying to figure out the image manager and placement editor.

4. Some of the plugins are extremely version sensitive. Trial and error solves this.

5. Some of the plugins that I want to use do not completely interface with the product - easy to solve but takes some time. I use tinyMce and it works when writing but not editing due to a path issue.

6. There are limited themes - about 25. That is changing rapidly.

7. As it currently stands, there is no allowance for categories, only tags.


Summary: I love how it works for a simple blog and the plugins to make it adult and SEO friendly are there (with a few bugs that are mostly path/theme related). That said, the documentation needs to be made clear and simple for the average blogger and some of the plugins need to be improved so the path issues disappear. I am going to plow through all of my issues and put a simple install and publishing doc on one of my sites, but it will take a few days. After I am able to do that, it will be a nice, clean, fast running, stable, customizable alternative to WP. I would advise, however, the technically uncomfortable to not venture there quite yet (at least until someone, me maybe, publishes some clean docs).

On Textpattern:

I uploaded textpattern to do a static site. I will say this, once configured and the site laid out, it will be a very clean and easy publishing device for both blogs and static pages.

The problem is, setting up the initial theme or customizing it takes mucho time. The buzz and support for the project also seems to have died, although they recently released an update.

I never made it very far with it because I concluded that it did not meet my immediate needs which were:

1. A simple, fast running alternative to WP for straightforward blogs.

2. A simple static site publisher for small, SEO driven sites on the 1000 plus inactive domains I have.

I will try it to develop a unique content static site one day as I liked the logic behind the platform, but that is another project for a another time.

Hope this helps. I do not think it helps you right now. I am,however, going forward with Habari and intend to figure out the bugs I am encountering, submit some fixes to the project, and publish a layman's guide. That is on the top of my list right now (I have some mainstream web publishing sites that will benefit traffic wise from doing this), but it will take some time, particularly at tax time here in the US.

[Useless]

For those interested, Habari installed effortlessly at Colo-cation and appears to work just fine. Here's test installation. http://www.maladaptedmedia.com/

Here's the simple method, disregarding their convoluted install directions:
-Download habari_makaanga.zip from here http://habariproject.org/dist/
-Extract its contents on your desktop or wherever.
-In the directory named 'user', you'll need to create two new directories; one named 'files' and another named 'cache'.
-Upload all of that junk to your host.
-Wherever Habari is going to reside add this to your .htaccess file:

### HABARI START
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
#RewriteBase /
RewriteRule . index.php [PT]
RewriteRule ^(system/(classes|locale|schema|$)) index.php [PT]
### HABARI END

...or create a new .htaccess file with that info if there is no file already present. (It will go in the root of your Habari installation. In other words, if Habari is being installed in a directory named, 'blog', your new .htaccess file would go inside the 'blog' directory, but not inside any of the directories that came with Habari. If Habari is being installed at the root of a domain, then Habari's .htaccess file would reside there outside of Habari's directories, just like the index.php file that comes with Habari.)
-CHMOD the 'cache' and 'files' directories so that they can be written to by your server. (755 or 777 should work.) (Habari will install and function without them, but you'll want them, especially the cache directory.)
-Call up your Habari installation, e.g. http://www.mydomain/index.php
-Fill in all the pretty boxes with the required information.
-After you hit the install button, Habari may bitch that it wasn't able to create a config file, but it will give you the code necessary for it. Copy and paste that information in to a new text file and name it 'config.php', then upload it to the root of your installation. (It goes right there with your .htaccess file and Habari's index.php.)

That's about it.

The post editor doesn't appear to be much of an editor at all. It's not what one would call a "rich" editor with all kinds of fun WYISWYG buttons. There may be a plugin for that though.

It's sort of nifty, like all new scripts are, but I haven't formed any opinion of it yet.

[whitey]

Originally Posted by Useless Warrior

For those interested, Habari installed effortlessly at Colo-cation and appears to work just fine. Here's test installation. http://www.maladaptedmedia.com/

Here's the simple method, disregarding their convoluted install directions:
-Download habari_makaanga.zip from here http://habariproject.org/dist/
-Extract its contents on your desktop or wherever.
-In the directory named 'user', you'll need to create two new directories; one named 'files' and another named 'cache'.
-Upload all of that junk to your host.
-Wherever Habari is going to reside add this to your .htaccess file:

### HABARI START
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
#RewriteBase /
RewriteRule . index.php [PT]
RewriteRule ^(system/(classes|locale|schema|$)) index.php [PT]
### HABARI END

...or create a new .htaccess file with that info if there is no file already present. (It will go in the root of your Habari installation. In other words, if Habari is being installed in a directory named, 'blog', your new .htaccess file would go inside the 'blog' directory, but not inside any of the directories that came with Habari. If Habari is being installed at the root of a domain, then Habari's .htaccess file would reside there outside of Habari's directories, just like the index.php file that comes with Habari.)
-CHMOD the 'cache' and 'files' directories so that they can be written to by your server. (755 or 777 should work.) (Habari will install and function without them, but you'll want them, especially the cache directory.)
-Call up your Habari installation, e.g. http://www.mydomain/index.php
-Fill in all the pretty boxes with the required information.
-After you hit the install button, Habari may bitch that it wasn't able to create a config file, but it will give you the code necessary for it. Copy and paste that information in to a new text file and name it 'config.php', then upload it to the root of your installation. (It goes right there with your .htaccess file and Habari's index.php.)

That's about it.

The post editor doesn't appear to be much of an editor at all. It's not what one would call a "rich" editor with all kinds of fun WYISWYG buttons. There may be a plugin for that though.

It's sort of nifty, like all new scripts are, but I haven't formed any opinion of it yet.

Thanks UW, you saved me the effort of putting that together for Ana and any of those interested. I would reiterate what I mentioned in my earlier post, however, about the fact that .pdo and inconv need to be enabled in php 5.0 or higher for it to work. Most hosts do not have them enabled by default - kudos to Colo for doing so as there is no good reason not to have them enabled.

One note: Use Firefox when using the script - I will explain why later as I am heading out right now.

FWIW, I have solved most of the issues that I think a pornblogger will be facing using the script - and there are text editor plug-ins (TinyMce amongst others). It is a very good platform for simple blogging - fast and intutive - and is an excellent platform for porting over posts written in html as it renders html and xhtml code effortlessly.

As an aside, the blog that I am developing on the platform is here: Masturbating Babes. It needs some sidebar and footer refinement as well as some SEO work on the home page, but is otherwise ready to launch after playing with the script for two days and resolving issues.