DragonflyCMS 10

[greenday2k]

Yeah, tons of changes almost daily!

Great, DF is breathing =)

[Dizfunkshunal]

DF lol has always been breathing

[NanoCaiordo]

Good news, I have LEO working on IIS 7!

IIS will require URL Rewrite module.

Both, Apache and IIS rewrite module will only need one rule.

All the rewrite is now done internally, soon in CVS!

[NanoCaiordo]

Plus I've got, always in local still, configurable url endings from admin settings.

Eg you can choose one of the following format:

/Forums.html
/Forums/
/Forums

[NanoCaiordo]

I need to know if you know of any module using "-" in its name.
Same for files used by the module in GETs.

Dragonfly allows more then the following, but I need to know if modules used all allowed characters or restricted them self to a-z 0-9 _

Basically I have expanded the URL capability of Dragonfly CMS but I need to know if it will break a module.

What I have:

/the-new-expanded-url
GET[name] = home page module
GET[file] = index
GET[0] = the-new-expanded-url

/My_Module/the-new-expanded-url
GET[name] = My_Module
GET[file] = index
GET[0] = the-new-expanded-url

/My_Module/entry/the-new-expanded-url
GET[name] = My_Module
GET[file] = entry
GET[0] = the-new-expanded-url

To get this working some changes will be required at module levels, and to avoid duplicates a (core or module?) table will be needed to fwd the title to the correct id.

Basically the home page module will be able to use the best URL, canonical link and permalink will be most likely required but I'll get to this later.

[greenday2k]

*I Like this.

I've checked my modules name files, custom and regular modules and None of them were using "-".

Some custom modules use friendly url's where "-" are used for SEO, but fixing and updating sitemaps/redirects etc is trivial.

[NanoCaiordo]

greenday2k wrote:

*I Like this. I've checked my modules name files, custom and regular modules and None of them were using "-". Some custom modules use friendly url's where "-" are used for SEO, but fixing and updating sitemaps/redirects etc is trivial.

Great you like it, I like it more lol ... in the last few days I've also been looking to support international url/folder/file support but nothing done yet.

Example of a URL?

It wont affect sitemaps, redirects, existing links etc etc as I'm adding capabilities that actually rely on the originals

[movix]

Hi everyone,

I followed the last posts with great interest. As you perhaps remember we talked allready about stuff like this URL rewritting. I just want to share some of my conclusions.

Quote::

... to avoid duplicates a (core or module?) table will be needed to fwd the title to the correct id.

This hits the point of the thoughts i had. Having such a relations will turn title into a primary key dind't it ?
what to do if to albums have the same name ? make a tunnel to allow the user to select the one he want's ? i did not found any clear way to handle this.

Anothing thing is that you must take care of the meta tags in case you end up with multiple URLs pointing to the same content ? i mean <link rel="canonical" href="masterURL" />

Not to borrow you, but if you're working on this and some new rules are given to modules, would it not be worth to think about the GET/POST variable "name" as i allready asked for ? You remember you replied that this would break all existing modules? Is there no way to keep backward compatibility ?

Last but not least as i'm near the border of germany and france i often think about content localisation. what i mean is having one url for the same content (news, store items, ...) in various languages chosen like the interface language upon the browser settings or the user choice.

I'm very exited about Dragonfly v10. I hope you will announce the release date as soon as you'll can estimate it. i'll promise to make the german and french translations if this offence nobody allready on this task.

[NanoCaiordo]

Technically:
This method will be able to run without a database table, but:

If a shared table holds all the data, the unique key will be "module id + pretty title", no primary key required.

If the table is going to be per module instead, then the solely key will be the pretty title.

Pratically:
There is going to be lot of freedom with it's use as long you understand that a straight url like "my-pretty-title" will always take you to index.php in the home module.

Duplicates can be resolved, without the need of a table, by adding the id: "2145-my-pretty-title".
Also module developers can then choose to add the date: "2012-05-08-my-pretty-title" or "2012-05-08/my-pretty-title".

Canonical and Parmalinks are nothing more then URL::index(), but will return the full LEO url, method will need to be modified or a new method will need to be done.

I already explained this, the way its done, it wont break any module or any existing url, it expands features

I believe Ertan will be looking after the German translation, but not sure.

[NanoCaiordo]

Oh with this feature it comes a high security feature as well

GETs have always been protected, but now they are rewritten unsetting anything that doesn't match the rules.

Module name: a-z A-Z 0-9 _
Module files: a-z A-Z 0-9 _
Other keys: a-z A-Z 0-9 _ -
Other values: a-z A-Z 0-9 _ ; : # -
Discharge the rest, your application wont even receive it.
Note: not considering international support yet.

Which means you could also use "2012-05-08=my-pretty-title", it gives freedom without hacking the core, the module decide how to write it and it's up to the module to use it ... add options for users about their preferred url? A lot can be done.

[movix]

Hi,

i looked a couple of time onto some V10 files.
what i noticed in index.php is that it seems that v10 is able to handle various sites with the same installation folder on the web server. Is that right ? If so that will be a great improvement and no more need to use symlinks !

[NanoCaiordo]

Yes, one source, multiple installs.
Working on it, I'm having few issues with it even because I would like it to handle module and theme installations separately for each install and so uploaded files ... see how it goes.

However one new feature I really like is added by Poodle.
Dragonfly now supports reading data from a slave database while saving to the master only.

There are lot of new features, some done or almost completed, some others barely wrapped.

[NanoCaiordo]

Oh to answer one of you earlier questions.

"name" is now a loader name, /include/load/name.php

You can copy "name.php" to "my.php" and I could probably make internal rewrites to be a little more dynamic so no files will need to be modified.

However "name" can be easily hidden from URL when using LEO.
LEO is also now supported in IIS6+ when a URL rewriter is installed in the webserver, just like apache.

[movix]

NanoCaiordo wrote:

However one new feature I really like is added by Poodle. Dragonfly now supports reading data from a slave database while saving to the master only.

WAOW awesome !

[NanoCaiordo]

You can decide to also have lower casing urls: "forums" instead of "Forums"

Canonical urls wont be added to html headers in the home page, but the header will be added in all others pages.

For example, if you change LEO from the classic "Forums.html" to "forums" the canonical URL will follow LEO settings so search engines when visit the cached "Forums.html" will see the canonical URL as "forums".

No redirects.

Am I missing something or this is good as it can be?