fixed conflicts with merging 1.1.1 into 1.2
fixed conflict issues
Merge branch 'dev1.1' into dev1.2
Merge branch 'dev1.1' into development
Merge branch 'dev1.1' into dev1.2
various changes and additions to Aisis to make it more flexable
Update README.md
Update README.md
Redone and readded the dev 1.2 branch for the new Aisis 1.2 that is scheduled for January 15th. We have included two new libraries, one will be a sperate product called 'Aisis Core' which is the core heart of Aisis Theme Framwork.
Made some minor changes and getting ready to start implementing major features.
Added a whole new section so that we can use twitter boot strap in the admin section. Started moving stuff around for the front end and how we wan't that to look.
I have added more stuff, fiex twitter boostrap and have yet to fix the carousel. I have also updated TWBS to 2.2.2 - which seemed to cause the issue with the carousel. This will be fixed. We have also managed to fix admin issues and removed the popover.
Cleaned up, fixed and added new features. Mini Feeds now display, popover and modals now work. Form elements are rendering properly
We now have made use of a factory pattern and created the appropriate class. We also have an index, we have a single post page. We also have a footer a new menu which is in the footer.
removed unwanted files
Fixed the loop being used and the contents of the loop. Fixed how we load and render files, Fixed a lot of various small issues including layout and other issues. Fixed admin side issues. Getting one step closer
We can now view post thumb nails, posts from categories and tags. We can also click on a tag and see its associated posts. We now have a category.php and a archive.php as well asa tag.php. The archive.php is a page template called archive
Lost of various changes and clean ups. We have fixed a ton of bugs and issues. We have also managed to clean up various templates, add forms and clean up code. Comments and documentation are next to come.
Added the abillity to add sub sections to forms. Each form can now have a sub section, they can only have one. How ever we are working on a way to allow for elements to have a sub section thus this means that if an element is interacted with you can use java script to hide the sub section and display it only if a checkbox is checked or a radio box is clicked on.
Seperated out the SubSection logic from the form into its own class with in the AisisCore, AisisCore_Form_Form and AisisCore_Form_Elements will extend this to allow for elements to have sub sections and for forms to have one sub section. If you extend Aisis_Form_Form and wish to make changes to or over ride the functions in AisisCore_Form_SubSection you must do that in the class that extends the AisisCore_Form_Form. PHP does not allow for multipl extensions. This is not in the AisisCore Development branch due to not being fullu implemented or documented yet.