Xinha Discussion Forum

The best way will probably be to send te code to gogo and also put up a demo of the plugins somewhere so people can check out how they look.

They look pretty good

All that's needed is to have the permissions by default filter down as read/write accessible from the 'root' given to the script by default. That way people who don't want permissions don't have to do anything other than set a path, while those who do can set/write a script to set the array of permissions.

Looks very nice.

Now we just need code shielding so PHP, etc. isn't lost when switching back to wysiwyg and it's sorted!

Sounds good, don't suppose you've got a working example up somewhere?

I have to say imho going back to the original plan (and your last suggested implementation goog) still looks the cleanest solution to the problem. Sometimes the simplest solution is the best

If you were to do something like that it'd probably need to be divs rather than spans as spans are not block-level elements and would appear on the same 'line' as each other unless set to display:block

I'll think about the rest of what's been said later as my brain's not up to it at the moment

That's what htmlspecialchars() is for. Can't say I've had any trouble with it.

I just put the content in the textarea as one normally would (run through htmlspecialchars() in PHP to avoid problems), e.g.

<textarea name="ta" id="ta"><?php echo htmlspecialschars($content); ?></textarea>

EDIT: added the PHP in to possibly explain better

The only problem then is that within the editor it'll appear with margins and that's where people will complain, so you'd have to edit the iframe code that Xinha uses to add the styled div and it's back to editing Xinha again.

On the permissions front, it should be possible to pass in an array of permissions follwoing the structure of the filesystem, along the lines of:

Array ( [0] => Array ( [/] => 7 [0] => Array ( [somedir] => 7 [0] => Array ( [somefile] => 7 ) [1] => Array ( [somefile2] => 7 ) [2] => Array ( [somefile3] => 7 ) ) [1] => Array ( [somefile] => 4 ) ) )

Hopefully people get the idea from the above, but basically you have a multi-dimensional array representing the filesystem where each file has a value attached to it that's the same as a linux permission (read/write/execute). Execute is obsolete for the purposes of ImageManager, but it doesn't hurt to have it in case someone finds a use for it.

When ImageManager then wants to display/move/whatever a file it can refer to the permissions array. For example, it only displays a file if the file's permission bit-matches with 4.

With a simple defined input like an array of names and numbers, people should fairly easily be able to input their own permissions to the ImageManager.

Thanks niko, I'll probably check it out sometime tonight and then put it up for download somewhere.