Forumlar / Unrelated / Offtopic / End of Seditio and LDU

Has anybody seen this?
http://www.neocrome.net/

End-of-life for the Sedito and Land Down Under products.
You can still find limited support in our Forums.

I have to say I was expecting that to happen. Seditio and LDU have always been a one-man show, which resulted in very slow development. I understand why Olivier made the decision to pull the plug. He's a grown man, with a family and a job. It makes complete sense that he wants to spend less time on Seditio, and more time with his family. Also consider the fact that he doesn't earn anything by working on Seditio, not even much respect and gratitudes anymore, I can imagine. It can also be depressing to see other (newer) systems gain a lot of attention very fast, while Seditio has been on the sideline for very long.

To be honest, the golden era of CMS systems is over. Big players like Drupal and Wordpress have the market, and that's not going to change any time soon. For us, this is one of the reasons to take Cotonti in a different direction, focussing on application development (as a framework) rather than just content management.

Heheh, thanks for the hint, maybe I'll include something like that on the new site ;-)

Update: Ok, new site will get AddThis.

Yes, and it's been quite active lately.

LDU 600 or 700 I believe was my first. ;)

But also, as I have seen with wordpress and all those big named CMS, my point of view stands as yeah there's more quantity but that overwhelms your ability to find true quality. When I see a CMS or CMF with millions of things to do it's just too much bull to sift through for me.

Added 4 months later:

#33271 Trustmaster:

Yes, and it's been quite active lately.

And it's back down?

#34889 Trustmaster:

Smb. hacked the site and Olivier didn't have time to restore it.

really 

Seditio was 'quite secure' for years because the hacks used weren't common knowledge back then. Nowadays there's far more people with knowledge about things like XSS, CSRF and other such techniques. Luckily Cotonti is still in active development and has much better security.

Cotonti has a system in place to prevent CSRF. It uses a security token named "x" and is stored in $sys['xk'] in the code. Cotonti automatically creates a hidden input field for every form, which contains the current value of $sys['xk'], so when the form is submitted, the token is sent along with it. Upon receiving a POST request, Cotonti automatically verifies the value of "x" to match the value of $sys['xk']. If it doesn't match, the request is denied and an error page is returned. The value of $sys['xk'] is changed regularly.

As an extension developer, you usually don't have to worry much about CSRF. If you use regular forms and send them using POST, Cotonti will handle the inclusion and validation of the security token automatically. However, if you're going to send stuff to the server using an AJAX POST request, you'll have to include the security key yourself. you can do this by simply using {PHP.sys.xk} in your tpl. For example:

jQuery.post(
  "{PHP.cfg.mainurl}/{PHP|cot_url("plug", "e=myplugin", "", 1)}",
  { x: "{PHP.sys.xk}" }
);

If you want to verify the security token in a GET request, you can use cot_check_xg().