Search found 147 matches

by Kellanved
Tue Jul 28, 2009 11:19 am
Forum: [3.0/Olympus] New features discussion
Topic: Global post queue functionality
Replies: 14
Views: 17289

Re: Global post queue functionality

1. Is there any way to disable the entire 'Newly registered users' group without setting the 'New member post limit:' to zero? I'm still struggling with why a post count limit field should have any control over what groups you get placed in but perhaps that can be explained as well. :? Groups are t...
by Kellanved
Fri Jul 10, 2009 8:51 am
Forum: [3.0/Olympus] Discussion
Topic: Extending the scope of the phpBB cache
Replies: 13
Views: 14923

Re: Extending the scope of the phpBB cache

There are numerous comparisons of include_once vs include and I am not familiar with the drupal one. The general trend is that the plain include (i.e. without once) is faster, with later php versions having equal performance for both. There are a few stating that 'include_once' is faster, but from t...
by Kellanved
Thu Jul 09, 2009 9:44 am
Forum: [3.0/Olympus] Discussion
Topic: Extending the scope of the phpBB cache
Replies: 13
Views: 14923

Re: Extending the scope of the phpBB cache

Perhaps the main one that leaps out is the would be to cache fully the WHO IS ONLINE data (say with a 120sec TTL) as this has an order N squared costs and there is no integrity penalty is the data is slightly stale. This would give a modest but worthwhile performance boost to (2). I added caching t...
by Kellanved
Mon Feb 09, 2009 12:33 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

Stallyon wrote:Do what I do. Quote, copy, paste, quote, copy, paste, post. It's like a long version of multi-quoting.
Go to the topic review under the editor. Mark the text you want to quote, click "quote" next to it. Rinse, repeat.

:)
by Kellanved
Sat Feb 07, 2009 1:35 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

We will re-start development ASAP. Sadly, our time is mostly spent with cleaning up the mess and that can't change for some time to come. We don't have the infrastructure to roll out updates at the moment. All team members are investing a lot of their time to get things in order again; this sad exam...
by Kellanved
Thu Feb 05, 2009 7:33 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

Hashing the old hashes again could be done; the tricky part is not to reduce password security when doing so. It adds another step of complication to conversions, though. We will probably introduce it. A switch as you propose, sadly, wouldn't have any effect. Admins already need a permission to acce...
by Kellanved
Thu Feb 05, 2009 1:11 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

Oh, I'm sorry. :D

Well, the thing is that few scripts are able to send out the volume of mails we require. We'll see when the time comes.
by Kellanved
Thu Feb 05, 2009 12:37 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

Sorry to say it so directly: phpMN has many more and worse security issues than phpList.
by Kellanved
Tue Feb 03, 2009 1:13 pm
Forum: [3.0/Olympus] Discussion
Topic: [Discussion] Downtime and Server Compromise
Replies: 353
Views: 238038

Re: [Discussion] Downtime and Server Compromise

No, the data of the old 2.0 installation was not present in the same database. The database solely held the 3.0 data.
by Kellanved
Mon Nov 10, 2008 1:04 pm
Forum: [3.0/Olympus] New features discussion
Topic: Template inheritance feedback.
Replies: 3
Views: 6610

Re: Template inheritance feedback.

I have changed the template path assignment. However, a template-level switch would have worked as well, i.e.

Code: Select all

<!-- IF T_SUPER_TEMPLATE_PATH -->
   ... do something with the super template's files ...
<!-- ELSE -->
   ... do something else 
<!-- ENDIF -->