[buggy snippet] Front End Document Manager (FDM) v0.1b

Quote from: Soda at Jun 27, 2007, 08:42 AM

- Suffix for friendly URLS: /
this part is added after your alias
ie your alias is "index" the suffix added is ’/’
normally you put ".hml" for the suffix this way the pagename is index.html
could you try and report back

I changed it to .html, but I still get the same (I made a new document and got /assets//events/sdfgdfgdsfg.html as the URL, when it should be /events/sdfgdfgdsfg.html). Is it a bad idea to have "/" as the suffix?

Quote from: Soda at Jun 27, 2007, 08:42 AM

Your tips is cool, but don’t work with add , you could simply test if fdmaction is not null (but other action do the same) or wait for the new version.

Yes I agree (but in my case I will have a single add button elsewhere -not in the ditto template-, so it does not have to work with add, so it is enough for me)

Tommy T.

new v0.0.98
I have changed the makeurl fonction to return relative path, editorpageid added but not fully tested.
@tommyt

Is it a bad idea to have "/" as the suffix?

I don’t know exactly.
could you try the new one and tell me if link are ok ?

Quote from: Soda at Jun 27, 2007, 09:55 AM

could you try the new one and tell me if link are ok ?

I have tried 0.0.98 and it the links are fine! (With "/" as the suffix as well, and editing documents does not create new ones). Will try to test the different edit page when I get a bit of time. Thank you!

Tommy T.

All work fine.
A litle bug. When i call fdm from ditto template i see @CODE: before buttons.
Whatzzzzzzzz up?

@swit4er
surely because you use russian chars, in chunkie.class.inc.php is :
$template=substr($tpl,6);
which I think cause the problem.
can you try this:
replace all "substr" with "mb_substr" and report back ?
update to 0.0.99, "@CODE:" placed in Template string

its all right! thanks Soda!

Great work !
Constant update I see you’re working full steam on this, and I didn’t even have a chance to give this a run that we’re almost there with a 1.0

There is one more thing that I would find useful: if the characters &, " < and > were translated into their html entity counterparts. after being entered in the front-end. This is because if the page is served as application/xhtml+xml, then a page with these characters will not validate and so not render at all in Firefox.

(I’m not an expert in php, but would this just be a call to htmlspecialchars at some point?)

Tommy T.

I’ve just realised: I would’t want rich-text fields to be escaped though: the characters " < and > should remain as they are... not quite sure how this can be achieved.

Tommy T.

Ok I’ve solved my own problem: using a #FILTER in the input elements that I want escaped, such as:

(So a great idea to use eform to process the forms!)

Tommy T.