Problems adding/modifying content

[heth]

I've got a site that's been using WB 2.6.7 for a few months, with MySQL4. It's a poetry site so reasonable amount of text and long page titles

The site works fine
I can log in to WB fine and view the pages
When I try to add new pages or modify existing pages though its suddenly prone to timing out but not all the time.

Are there any limits on how much data WB can handle? I notice that the page description is an index in the database... is there a limit to how much it can handle as a index?

I know its not the server because another site on the same server is updating lightning fast

Any ideas?

[heth]

update... I compared the database with another cms and it seemed that the page content was being indexed but not in the other cms. So I dropped the index on the database

Thought I had it but not seeing any difference

[heth]

update

I tried to remove a space that appeared at the start of a line and it consistently timed out.
Then I tried removing the same space and the line of text above it and it did it straight away

Another time I typed random text on a new line and it timed out
Type the same text on the end of the previous line and it saved

The problem seems inconsistent but is producing behavioural patterns

It feels like a problem in the way WB is storing to the database

Really hoping someone's got some ideas

[thorn]

Hello,

there is a known issue with wb2.6.7 and a very special apache-config -  triggered by AddDefaultCharset in apache.conf and use of umlauts (specialy 'ü').
Do you use umlauts?

Solution:
Try to create a .htaccess-file in website baker's root-directory

Code:

php_value default_charset utf-8

or
use ISO-8859-1 in website baker
or (best solution, if possible)
set AddDefaultCharset Off
in apache.conf

thorn.

[heth]

no, I'm not using umlauts.

But I will try your suggestions in case it makes a difference.
I've just had another customer complain of the same timeouts. This is since the server was migrated

[heth]

WB times out when I try to change the character set

The server won't let me create an .htaccess file

I've looked for apache.config and can't find it... where would I find this?

I'm thinking more and more that this must be to do with the server migration but sometimes the page will save and sometimes it won't. Why? It really feels like a filesize/pagesize issue but two pages that are causing the same problems have differing total of characters by 200.

Grrrrr, this is really causing me aggravation

[BerndJM]

Hi,

I've looked for apache.config and can't find it... where would I find this?

- what OS?
- what Apache Version?
- you're allowed to change the server configuration?
- is it "your" dedicated server or a shared hosting account?

Regards Bernd

[heth]

- what OS? Windows 2003
- what Apache Version? I've checked with the host - it's not using Apache, it has IIS v6
- you're allowed to change the server configuration? No
- is it "your" dedicated server or a shared hosting account? It's shared hosting

[BerndJM]

Mahlzeit

it had been nice to get those information together with your first post

cite from "requirements":
Please note: WebsiteBaker is known to be fairly Operating System independent, however it may be tricky using on a non *nix system. WebsiteBaker is developed on Ubuntu Linux and also is officially tested on Debian Linux servers.

You're wondering, that you cannot find the apache config when your host runs an IIS ... you're really wondering?

 
Bernd

[heth]

ok, my apologies for not being knowledgeable in server configs. I'm an html editor and WB has always been easier enough to setup for me to not be an expert.

i've had sites working perfectly on this config for over a year. The problem has occured since a server migration. Nothing has changed on the server other than physical machine (server was cloned to new hardware)

[heth]

I've found that one of my wb sites, has a difference in the structure in that most of the tables show "InnoDB" as the type. In the ones that aren't working, "MyISAM" is the type on all tables

Could this make a difference?

I tried editing text directly into the mysql database and got a message saying "Because of its length, this field might not be editable". But on a page with less content, it let me update without any problem... which is exactly the problem i'm having from the front end

unfortunately, my hosting support guy can update it. myself and my customer can't

This is driving me nuts