srpurdy / SharpEdgeCMS

Content Management System
http://www.sharpedgecms.com/
MIT License
18 stars 4 forks source link

Codeigniter 3 #35

Open srpurdy opened 9 years ago

srpurdy commented 9 years ago

The time has finally come. Codeigniter 3 RC3 was just released. We are expecting The final version is not too far around the corner. So for this reason the planning stages of updating shapredge to support the updated Codeigniter framework has begun. This is a fairly large update to the CodeIgniter framework. So a lot of changes will need to happen in sharpedge to make it compatible. The important news is it is now on our list of up coming updates. Right now I am in the stages of identifying what changes need to be done within sharpedge. So I don't have any specific timeline on completing this update, but I will update this issue with more information when it becomes available.

srpurdy commented 9 years ago

Small update on this issue. I have gone through everything to see what changes will need to be made to update the system. I've debated back and forth on doing it as Version 4 of SharpEdge, or to write a bunch of update routines. I'm not completely decided on this yet, but am leaning towards writing update routines. A lot of big changes have been made in codeigniter. It is why I am questioning which direction to go. In either case I hope to have more information on in regards to CI3 in the not too distant future.

mannym commented 9 years ago

It would be good to make it compatible with other existing cms modules.

srpurdy commented 9 years ago

What do you mean compatible with existing cms modules? Do you mean so a module built for wordpress can be used in sharpedge?

mannym commented 9 years ago

better modules to Processwire, it looks nice.  only a suggest. Best regards.  sorry for my bad english  

 El Miércoles 1 de julio de 2015 8:33, Shawn Purdy <notifications@github.com> escribió:

What do you mean compatible with existing cms modules? Do you mean so a module built for wordpress can be used in sharpedge? — Reply to this email directly or view it on GitHub.