this month and the coming two months, starting from today, so providing
information for the future or the past is only an illusion. Only the
recurring events are displayed on those pages, so there is no point in
serving them.
is allowed for historical reasons, two years forward
is allowed for those organizers who know two years in
advance, what they will present...
This should make the cal page indexable by local search
engines too...
- Indentation standardisation
- Added several comments
- Made some file reads and variable
checks more error-proof, so it gracely
degrades from more problematic situations
Still nothing done about year problems, I am on it...
Goba
mysql-free. also got rid of events.php, since cal.php can now display info
about particular events. the calendar should look essentially the same, modulo
smaller default text, and some small css tweaks (mainly to put a divider
between events -- i could never tell them apart before).
one small thing to add would be a remove button to events a-la the
manual notes when the magic cookie is set.
realized, that he is not the primary site, then redirected
to php2.chek.com, but that is again not the primary site,
so redirected to php2.chek.com and so on... Now test for
php2.chek.com
I have mirror sites fetching a CSV from www.php.net once every 6 hours.
As far as I can tell this should work just fine, but let's keep an eye
on this concept and see if it actually does. The code is written such
that if for some reason a mirror can't get or can't save the CSV, it still
works but just doesn't show the upcoming events.