Did you know that Monty Python actually inspired ppl to use the word SPAM for unwanted advertising? Here's how they did it:

Monty Python Spam Song

Scene: A cafe. One table is occupied by a group of Vikings wearing horned helmets. Whenever the word "spam" is repeated, they begin singing and/or chanting. A man and his wife enter. The man is played by Eric Idle, the wife is played by Graham Chapman (in drag), and the waitress is played by Terry Jones, also in drag.

Man:
You sit here, dear.

Wife:
All right.

Man:
Morning!

Waitress:
Morning!

Man:
Well, what've you got?

Waitress:
Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam; spam bacon sausage and spam; spam egg spam spam bacon and spam; spam sausage spam spam bacon spam tomato and spam;

Vikings:
Spam spam spam spam...

Waitress:
...spam spam spam egg and spam; spam spam spam spam spam spam baked beans spam spam spam...

Vikings:
Spam! Lovely spam! Lovely spam!

Waitress:
...or Lobster Thermidor a Crevette with a mornay sauce served in a Provencale manner with shallots and aubergines garnished with truffle pate, brandy and with a fried egg on top and spam.

Wife:
Have you got anything without spam?

Waitress:
Well, there's spam egg sausage and spam, that's not got much spam in it.

Wife:
I don't want ANY spam!

Man:
Why can't she have egg bacon spam and sausage?

Wife:
THAT'S got spam in it!

Man:
Hasn't got as much spam in it as spam egg sausage and spam, has it?

Vikings:
Spam spam spam spam... (Crescendo through next few lines...)

Wife:
Could you do the egg bacon spam and sausage without the spam then?

Waitress:
Urgghh!

Wife:
What do you mean 'Urgghh'? I don't like spam!

Vikings:
Lovely spam! Wonderful spam!

Waitress:
Shut up!

Vikings:
Lovely spam! Wonderful spam!

Waitress:
Shut up! (Vikings stop) Bloody Vikings! You can't have egg bacon spam and sausage without the spam.

Wife:
I don't like spam!

Man:
Sshh, dear, don't cause a fuss. I'll have your spam. I love it. I'm having spam spam spam spam spam spam spam beaked beans spam spam spam and spam!

Vikings:
Spam spam spam spam. Lovely spam! Wonderful spam!

Waitress:
Shut up!! Baked beans are off.

Man:
Well could I have her spam instead of the baked beans then?

Waitress:
You mean spam spam spam spam spam spam... (but it is too late and the Vikings drown her words)

Vikings:
Spam spam spam spam. Lovely spam! Wonderful spam! Spam spa-a-a-a-a-am spam spa-a-a-a-a-am spam. Lovely spam! Lovely spam! Lovely spam! Lovely spam! Lovely spam! Spam spam spam spam!

The SPAM song is here: link to wav file

The whole sketch on Google Video

Enjoy!

Herko

This is the XOOPS open source CMS support site, not the netbus/hotcat support forums. Please contact the sowftare authors for more information.

Herko

I agree these are very good ideas

One thing tho: the 2.0.16 was the last release in the 2.0.x series, and all core development efforts are focussing on 2.3 from now on. This is announced on sf.net (the core dev discussions) and in the 2.0.16 release news as well.

Consequence of this is that improvements for the 2.0.x core will not be implemented into any official release of that series.

A possible solution would be to focus on geting these great ideas coded into the 2.3 releases as soon as possible (and with that I mean as soon as the 2.3 code allows details such as this to be added).

One thing I like about that solution is that there's an active user-driven collaboration in the 2.3 development.

Downside of this is that it requires everyone to think outside of the 2.0.x/2.2.x box and start thinking in the 2.3 framework, and not many people and developers have given that a serious go (as is shown by the level of collaboration on the alpha releases up till now).

What about selecting a set of user-driven features and improvements, and getting a few people to code them for 2.3? I mean focus the effort and necessary skills and mindset, so as not to make 2.3 weaker because of poor quality coding or flexibility/scalability issues.

Just my 2 cents.

Herko

I stand corrected

Please note that this hack prevents proper migration to newer versions of the XOOPS core (as with any hack), unless you know what you are doing (as with any code changes).

Herko

Any results when you trun php debug on and try again?

Herko

difficult to say. Most of the time speed aka performace issues are due to the configuration and resource availability of the server the site is hosted on. Performance depends on available memory, number of open connections, session durations, concurrent users, number of active processes on the server, availability of CPU time, available bandwidth, installed server extensions, load balancing configuration, caching infrastructure, activity of other sites on the server... The list probably goes on for the initiated.

The script running on the server is but one factor. It could be because of XOOPS 2.2.x, but from the problem report 'my speed is gone' it is rather difficult to make a decent analasys.

Check with your hoster to find out what is causing the dramatic reduction of speed.

Herko

here we go again... must be the time of the year (christmas is coming...).

Do a search for 'mascot', and see what has been said and done about this

This is not to stop this initiative, but to bring it up to speed.

Herko

simple. you can't, at the moment. Nor is this planned in the near future.

Herko

is there a /modules/tag/ folder with that specific file? You say you're only working with the article module, not the tag module.

Herko

p.s. please keep your threads in one place ata a time, that way people will know when something has been answered, and won't invest time to investigate a possible solution for you when it is no longer necessary. You don't like it when that happens to you.

already answered on www.xoops.nl.

The line should read
include XOOPS_ROOT_PATH."/modules/tag/list.tag.php";

(note: the . should be before the "path/to/the/file.php";)

Herko