Development Discussion Board

software version number 4.0 has a long and bloody history as a very bad number, at least since the dawn of the PC era.
some of us are old enough to remember the fiasco that was DOS 4.
NT 4 was not *that* bad, but is was a low point in the NT line (not as low as windows ME or vista, but still much ...

I say let it die. Barely any MOD Author's support it, and there are very few sites that use it/style based off of it.
you may be right and you may be wrong, but it will help if you tell us, how do you know?
specifically, how do you know how many sites use it?
is there any statistics, or you mean ...

the distinction between actions and filters is 100% artificial.
a "filter" call can do stuff in addition to changing the data (indeed, how can you prevent it from doing stuff? it's php code supplied by a 3rd party, and if they choose to do stuff they will), while an "action" type call should also be ...

if you look at the hook system implemented by phorum, it would answer both your questions.
it is *not*very expensive (performance-wise). actually, it's extremely lightweight.
it *does* support hooking-inside-templates.

you are right in that moving in this direction requires work, but this is no ...

(please forgive the "backseat moderation")
imo - should be moved to "RFC" forum.
mod - if you decide to do that, i would be grateful if you can remove this post while at it.
thanks.

maybe....
i am not sure if this is the case - i did not actually read all the recent changes to the code.
however, i thought of something that may make life easier (or not). if i'm wrong in my assumption, or if it doesn't make life any easier just scrap it.

so here goes:
IMO, global announcement is ...

Actually, unless I'm very mistaken there is logic in there which parses all the @imports. How else would we get the whole stylesheet into the database?
surely we interpret the @import when compiling style.php, but this does not necessarilly mean we take it into account when *deciding* to recompile ...

oh well....
at least i'm glad you guys are fixing it going forward.
thanks.

peace.

3.0.7 contains new content in the .htaccess, so it needs to update that file... That is why it's in the update package, that's not a bug. :) if it breaks existing installs it *is* a bug, even if you (or anyone else) refuse to accept it.
saying something like "we don't have to support any back ...

how about just create a special "global announcement permission" which is absolutely completely promiscuous, and use it for all global announcements? this can completely bypass the $auth->acl_getxx mechanism for global announcements?
just a thought.