the old static page can be seen at www.balatacamp.net
i'm having some trouble implementing the bidi module that alaa developed. I copied the bidi.module file into the module directory and enabled it from administer --> modules. but it doesn't seem to be taking effect. am i just stupid and forgetting to enable the bidi somewhere else?
and if ppl are busy just ignore this, but does anybody know if the /files/ folder and its subfolders need specific permissions for the 'upload' and 'image' modules to work? will 760 do the trick? i'm having some problems getting either of those modules to work, and haven't worked out what yet.
its a filter module
Bidi is what we call a filter module.
unfortunatly this is not covered properly int he drupal docs, filter modules allow you to create different "input formats" where the text you input in a node or comment textarea is transformed before rendering the node.
bidi is a filter module that scans each html block and computes its line direction then adds a class="right2left" or class="left2right" attribute.
in order to use bidi you must add it in your input formats (administer->input formats then choose configure for each input format), and bidi would better be the last filter applied.
finally your theme style.css file should contain something like
.right2left { direction: rtl;} .left2right { direction: ltr;}I also suggest you use the html correcter filter module and put it before bidi in the list of filters for each input format, bidi assumes correct nesting of html tags and since its a dirty hack there is no guarantee it will cope well with faulty input.
did this make any sense?
please in the future use seperate posts for each questions.
the files directory should be writable by the user running the apache webserver (might be apache, http-data, nobody, daemon, etc depending on distro).
so it needs to be at least 770, but if you can't chgrp the dir to the apache group then you might have to use 777 instead.
on my servers I make sure the directories group is apache and use 2770 the setgid bit ensures that directories created inside files/ will retain the same permission and ownership.
Alaa
"i`m feeling for the 2nd time like alice in wonderland reading el wafd"
IMHO
argument 2 is $format, check your input format settings for anonymous and compare it with the settings for auth. user, maybe that might help. Complain, do nothing, get your free Patagonian identity.
never noticed
I never noticed the second question, remember one question per thread.
files/ needs to be writeable by the apache process, so either 770 or 777 depending on the group ownership of the dir.
Alaa
"context is over-rated. who are you anyway?"
Why the 7
Why the second or third 7, I'd give it a 6, no need for such a permission in such a directory. IMHO it might better be a 760 or 764. Complain, do nothing, get your free Patagonian identity.
because files/ is where
because files/ is where uploaded content goes, pache needs to be able to write there.
Alaa
"context is over-rated. who are you anyway?"