Submitted by khaledhosny on Mon, 10/04/2006 - 14:06.
( categories: )
عند محاولة البحث داخل الموقع باستخدام كلمات عربية, لا تظهر نتيجة البحث ويظهر بدلا منها رسالة الخطأ هذه
Fatal error: Maximum execution time of 30 seconds exceeded in /home/.devil/eglug/eglug.org/includes/common.inc on line 378


works fine here, What's
works fine here, What's the word you used ?
WWW: The place for organized randoms!
الغة
الغة العربية
العربية
ام بلاير
بلاير
My blog
عندك
عندك حق
!!!
WWW: The place for organized randoms!
طيب وايه
طيب وايه الحل؟
My blog
ما
ما اعرفش
المفروض ان فيه مدير جديد دلوقت غيرى بس واضح ان باقى المديرين نايمين و مش واخدين بالهم
خلاص انا بره! اتصرف معاهم بقه ;-)
WWW: The place for organized randoms!
:P
until now ur still not out :P we need diaa and phaeron approval on the new admin.
Khaled okay i'll check it give us some time please.
peace
Live Free Or Die Trying...
GPG Key ID:0x6FD809F4
They did approve 6 days
They did approve 6 days ago.
BEside, I have no connectivity at home these days.
WWW: The place for organized randoms!
Donn
they should approv now as the post saying , may be someone changed his mind or something. been more than 1 day and 2 already didn't post ;-)
peace
Live Free Or Die Trying...
GPG Key ID:0x6FD809F4
hi. back from the dead. I
hi. back from the dead. I too had no internet at home for a few days, and was busy at college for 72 hours continuous.
I approve.
temporarily fixed..
yeah, temporarily fixed.
I found that this node: http://www.eglug.org/node/1335 is what was getting forever to load (yes, even normal node access was looping forever), thus causing php to force-stop it. Why?
I can't precisely tell, but anyway, the filters for the "Mixed Wiki and HTML" input format was producing too broken HTML. Bidi module (which handles line directions) doesn't like this broken result, and keeps looping forever to calculate its directions.
The Fix: no code fixes, sorry, I temporarily modified the node content itself, to give the same result but with different syntax, to overcome bugs in filters so they give proper HTML. After that, both worked happily.
Anyway, there may be more broken nodes that will fail too. So for a proper fix, we actually need to fix two things:
If anyone is interested in the (old) content for this node that caused the problems (for reproducing the error in order to produce a fix, for example), it can be found here.