#legacy

Rastin Mehr

Rastin Mehr

It may not seem as exciting to you guys, but removing #joomla #legacy code from Anahita is such a pleasurable experience. It is a path to a lighter system. The module manager and the entire module system is next. #Anahita #hackathon
Rastin Mehr

Rastin Mehr

The #legacy #joomla Menu Manager has been removed successfully. The code hasn't been merged with the master branch yet. #Anahita #Hackathon
Rastin Mehr

Rastin Mehr

  • September 17 2014
Reminder that Friday and Saturday are the weekly #Anahita #Hackathon days. This week's focus is extracting the #legacy #joomla menu manager from the 4.0 codebase.
Rastin Mehr

Rastin Mehr

Strict Standard Warnings

When using Anahita on PHP 5.4 and later there are strict standard warnings in Joomla, Nooku, and even Anahita code. Of course they can be suppressed in the php.ini file, but they make it very difficult to develop for Anahita when the developer needs to see all errors and warnings. Fix all the strict standard code in Anahita and current release of Nooku and the Joomla code that is going to be wi...
Rastin Mehr

Rastin Mehr

Default template record is removed when a template is saved.

When a default template is saved, the flag that says it is the default template gets removed. #bug #legacy #joomla
Rastin Mehr

Rastin Mehr

All the menu modules have been removed and now the menus are just standard layouts in templates html/menus and they can be overwritten within your custom templates. The dispatch of Anahita is still relying on the JMenu object. Once we untangle that, then we should be able to remove the module manager component and tables from Anahita. The code has not been merged yet and you can find it here ht...
Rastin Mehr

Rastin Mehr

Most of the features for the #Anahita 4.0 release are implemented now. The next 4-5 weeks we will be focusing on taking out #Joomla #legacy code and refactoring some of the Anahita native code. Some of you may not like it, but modules and menu manager will be removed.

Powered by Anahita