Pligg V2.0

[AshDigg]

Pligg V 1.0 information here.

Demo's coming soon.

A complete rewrite of Pligg has been started to
- improve performance
- ease templating
- improve language support

There are 2 'editions' that I am working with at the moment.

Not MVC) Rewritten code with various freely available classes. Not using Smarty or TemplateLite. Turns out we don't use most of the features and we simply don't need it.

MVC) Rewritten code using the CodeIgniter framework. Anyone not familiar I encourage you to checkout these videos. I've tried Cake, Symphony and Zend but I felt most 'at home' with CodeIgniter.

Code is available for review, just PM me.

Both 'editions' are at the same point in the development process. Both can
- work with Beta 9.x data
- display stories
- allow voting / unvoting
- allow submitting of stories
- allow register / login / logout

Both 'editions' are 10-100 times faster than the Beta 9.x series even without any caching enabled.

We have not decided which 'edition' to continue with. At this point in time, it looks like we will go with CodeIgniter due to the enormous amount of 'classes / features' that comes with it, and it took much less time to develop than 'non mvc' 'edition'.

Both versions are far enough along to support a 'feature request' site run on Pligg V2 for submitting / voting on new feature requests.

more information (and maybe better editing) (and maybe less single quotes ' ) to come.

[P1mpPanther]

is there a demo site running v.2 yet?

figured id ask...

[Tarindel]

what does this mean for the projected release of v1.0? Is 1.0 scrapped now in favor of 2.0?

[AshDigg]

Pligg V 1.0 information here.

Demo's coming soon.

[harlem]

Any details on the upgrade path? For instance, I am using 9.1. Should I incrementally upgrade to each successive version. This information would be good to know before upgrading to a stable release.

[dollars5]

Quoting from CodeIgniter site

CodeIgniter is right for you if:

* You want a framework with a small footprint.
* You need exceptional performance.
* You need broad compatibility with standard hosting accounts that run a variety of PHP versions and configurations.
* You want a framework that requires nearly zero configuration.
* You want a framework that does not require you to use the command line.
* You want a framework that does not require you to adhere to restrictive coding rules.
* You are not interested in large-scale monolithic libraries like PEAR.
* You do not want to be forced to learn a templating language (although a template parser is optionally available if you desire one).
* You eschew complexity, favoring simple solutions.
* You need clear, thorough documentation.

These highlighted things are of particular interest.

[Yankidank]

For everyone who is concerned about upgrading, Pligg 2 will connect to your existing Pligg Beta mysql. So your site should be able to continue to use your current Pligg data using the new framework.

[not2serious]

Since we now know that the easy template integration will not be available until v2.0, is there any anticipated release date? Even if it is a rough goal date.

This may encourage the creation of some new templates for v9.x thru the v1.x (since there will be only limited new features). If the investment of time and money will have a useful life of 6 or months, the template developers may be willing move forward and actively develop new templates.

[fujipadam]

Originally Posted by Yankidank

For everyone who is concerned about upgrading, Pligg 2 will connect to your existing Pligg Beta mysql. So your site should be able to continue to use your current Pligg data using the new framework.

So when Ash is doing a complete rewrite its just the code and will not be changing the DB schema?

And ofcourse being the noob I am I have to ask again, will the 1.0 version have the new code or any of it? or is the re-write only for 2.0

[dollars5]

The CI will be used for v2.0, v1.0 will be based of the current code base.