XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


(1) 2 »


1
naish
Re: Xoops causes segmentation faults under high load.

  • 2004/2/6 6:45

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Thanks for the advice.

We are already logging all errors to an error file, but nothing shows up there. No php errors at all.

But we are going to try and get a coredump ASAP.

Kind regards
Michael
Topic | Forum


2
naish
Re: Xoops causes segmentation faults under high load.

  • 2004/2/5 14:49

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Thats the problem, the process segfaults before it writes anything to the access_log, thus it is empty.

There is no core dump either, we are currently looking into building apache/php with debug options.

I seem to recall that xoops.org once suffered from "blank pages" and that it suddenly went away. Anybody know what happened there? It would seem that we are the victims of the same problem.
Topic | Forum


3
naish
Xoops causes segmentation faults under high load.

  • 2004/2/5 13:23

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


We just went live with our XOOPS site: www.fyn.dk

And now we get a lot of these errors:

[Thu Feb 5 14:15:33 2004] [notice] child pid 3033 exit signal Segmentation fault (11)

We have been unable to track the problem down. On a sister server (not using xoops) we have no problem whatsoever.

Ideas and suggestions are most welcome

Michael
Topic | Forum


4
naish
Re: prevent xoops module installer from parsing the templates?

  • 2004/1/11 9:48

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


The problem described in this thread stems from the fact that XOOPS need to "run" the template in order to recompile it. This is a limitation in smarty AFAIK....

The best solution is to make smarty compile only, however there seems to be no function to do this.

The <{if $objectname}> seems to be the best workaround available..

This is not a good thing IMHO, but I currently don't know how to fix it.

Topic | Forum


5
naish
Re: The admin menu

  • 2003/11/5 14:41

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Okay, now I have cleaned it up somewhat and even made a small change.

Menus now show/hide when you click on them.

The Url is still the same cp_functions

The instructions above still apply.
Topic | Forum


6
naish
Re: A full page cache

  • 2003/11/5 12:58

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Sure, I will dig into it, it doesn't seem that hard. Especially because I have working code to copy from.
Topic | Forum


7
naish
The admin menu

  • 2003/11/4 13:22

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Hi everyone.

I have noticed a big problem with the XOOPS admin menu as it is today.

The floating menus get in the way and you hit them by accident way too often.

I have made a rough patch that will create a more user friendly menu.

Get it at cp_functions

You have to replace include/cp_functions.php with the new file and delete your cache/adminmenu.php file.

This is a ROUGH patch and will have to be cleaned up, but if enough people like it I will clean it up.

WARNING DO NOT APPLY THIS TO A LIVE SITE. YOU HAVE BEEN WARNED
Topic | Forum


8
naish
Re: A full page cache

  • 2003/11/4 13:12

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Okay how is it supposed work and will it be a general solution for all platforms?

I would like more info as our team needs a full page cache by January 1st.

Otherwise we are going to look into solving this problem.

How about it?
Topic | Forum


9
naish
A full page cache

  • 2003/10/31 9:34

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


A thing that I find is missing from XOOPS is a full-page cache.

It would be nice if we could set a module to cache the complete html-page instead of just its parts.

Of course this could only work for GET requests, but it has the possibility of speeding up XOOPS by a large order of magnitude.

Preliminary tests indicate that XOOPS can do about 14.4 MB/s of html, versus almost 50 MB/S with a "hacked cache" on the same machine.

I would like to know what people think of such a cache?

Topic | Forum


10
naish
Re: Center block ordering

  • 2003/10/31 9:19

  • naish

  • Just popping in

  • Posts: 21

  • Since: 2003/6/10


Actually it touches on a major weakness of Xoops.

1. Block order is static. Either you have:

center
left - right

left - right
center

This problem could be solved if we were to create a "Superblock" module that could do more advanced layout stuff. That way the superblock module would publish blocks containing other blocks. Think of the way java.swing does gui layout.

I might look into this in the not so far away future.

2. In XOOPS you can do block layout on a module basis. That is you can place a module on the top page or on a module page. A more flexible solution would be to let modules publish a list of pages that blocks could be placed on.

This feature is very important for commercial/complex websites. Currently my team is doing ugly hacks to get around this limitation.
Topic | Forum



TopTop
(1) 2 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

160 user(s) are online (103 user(s) are browsing Support Forums)

Members: 0

Guests: 160

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits