16
Quote:
Bender wrote:
Ok, here we go.
First to be said news is a very common and widely used module. If this were a general problem of the module there should(!) be more reports of this kind of issue.
Not guaranteed but more likely therefore this is caused by the configuration of your server in combination with this specific version of XOOPS or news module or some problem with the database.
Could be.
Just for sure: how much the "keywords" and description" take time in database operating?
Now what i would do is this:
Quote:
- download the site. set it up locally using Xampp for example and see if it shows the same behavior
Ok, I'll try to do it.
Quote:
- setup another fresh XOOPS on your webserver into a subdomain and (separate) database and see if it also happens there
- dump a copy of the news tables into that test setup again checking if it happens also
This should give some more clues in which direction to continue searching.
Well, first I setup a fresh 2.0.14 with 1.44 in a new database (empty one), and everything work fine.
Also, some more tips. It works well in the morning, but lousy during the evening.
Quote:
Also you said you had troubles when upgrading and messed around in the database manually if i am not mistaken. Did you try to optimize/repair tables afterwards?
This is a problem. Some big tables I ussualy can't repair, and "stories" is big (20 MB). When I do it, base colapse and nothin woorks for several minutes.
Ok, I'll add this: "stories" encrease their size each time i post na new article a lot. Then I must perform optimize, and after that base crashed and become unreachable for several minutes, then it appears with decreased size.
