burstcms - Google Code

Earlier this year Apr 30, 2009 issue 19 (Data types supported by BurstCMS table creation API) Labels changed by voyagerfan5761 - I would add text, at the very least, to k00pa's list. BurstCMS is, after all, a CMS, and it will therefore need to store blocks of text that will be too long for varchar fields. Labels: Type-Other Priority-High Milestone-0.1 −Type-Defect −Priority-Medium I would add text, at the very least, to k00pa's list. BurstCMS is, after all, a CMS, and it will therefore need to store blocks of text that will be too long for varchar fields. Labels: Type-Other Priority-High Milestone-0.1 −Type-Defect −Priority-Medium Apr 30, 2009 issue 10 (dev_database_template.sql don't contain any example data) Status changed by k00pa.pelikoira - Oops... not yet verified Status: Fixed Oops... not yet verified Status: Fixed Apr 30, 2009 issue 10 (dev_database_template.sql don't contain any example data) Status changed by k00pa.pelikoira - Solved this problem, but hashing not done... And I think that that is not supported by postresql... Status: Verified Solved this problem, but hashing not done... And I think that that is not supported by postresql... Status: Verified Apr 30, 2009 issue 19 (Data types supported by BurstCMS table creation API) commented on by k00pa.pelikoira - I think we need to support the most common types that are supported by both databases. next types _must_ be supported: int varchar timestamp I think we need to support the most common types that are supported by both databases. next types _must_ be supported: int varchar timestamp Apr 30, 2009 issue 11 (No user registration) commented on by k00pa.pelikoira - Registering could be at backend. Disabling/enabling registering could be done with BURST_ALLOW_NEWACCOUNT variable that is on global config file, admin interface of course would have ability to modify this easily. Registering could be at backend. Disabling/enabling registering could be done with BURST_ALLOW_NEWACCOUNT variable that is on global config file, admin interface of course would have ability to modify this easily. Apr 30, 2009 issue 2 (Absolutely no admin interface) commented on by k00pa.pelikoira - possible248, I disagree with api. I think admin interface should be build from modules. If there is next modules on burstcms: poll,pages,guestbook. Then those modules could have poll_admin,pages_admin,guestbook_admin modules that can be used trough admin interface. This would be much easier to do and it would be much more flexible than custom api for admin interface. possible248, I disagree with api. I think admin interface should be build from modules. If there is next modules on burstcms: poll,pages,guestbook. Then those modules could have poll_admin,pages_admin,guestbook_admin modules that can be used trough admin interface. This would be much easier to do and it would be much more flexible than custom api for admin interface. Apr 30, 2009 WikiIndex (The wiki home page.) Wiki page edited by k00pa.pelikoira Apr 30, 2009 BurstPathConfig (Guide to modify burst_paths.php) Wiki page added by k00pa.pelikoira Apr 30, 2009 r150 (Started to create admin interface, it should now work with a...) committed by k00pa.pelikoira - Started to create admin interface, it should now work with admin module loading... Started to create admin interface, it should now work with admin module loading... Apr 30, 2009 AdminInterface (Describes how admin interface is loaded, used and renered) Wiki page added by k00pa.pelikoira Apr 30, 2009 r148 (Added the getIsAdminModule () function to example module.) committed by k00pa.pelikoira - Added the getIsAdminModule () function to example module. Added the getIsAdminModule () function to example module. Apr 30, 2009 r147 (Added BURST_THEMES_PATH variable.) committed by k00pa.pelikoira - Added BURST_THEMES_PATH variable. Added BURST_THEMES_PATH variable. Apr 30, 2009 WikiIndex (The wiki home page.) Wiki page edited by k00pa.pelikoira Apr 30, 2009 ModuleSettingsFileSyntax (Creating module settings files) Wiki page edited by k00pa.pelikoira Apr 30, 2009 r144 (Changed paths to right directory...) committed by k00pa.pelikoira - Changed paths to right directory... Changed paths to right directory... Apr 30, 2009 r143 (Cleaned devunitys stuff, and started creation of admin inter...) committed by k00pa.pelikoira - Cleaned devunitys stuff, and started creation of admin interface Cleaned devunitys stuff, and started creation of admin interface Apr 30, 2009 r142 (Commited) committed by k00pa.pelikoira - Commited Commited Apr 29, 2009 r141 (Added some test/dev data to development template. Passwords ...) committed by k00pa.pelikoira - Added some test/dev data to development template. Passwords should be crypted, but we have not decided how to crypt them... Added some test/dev data to development template. Passwords should be crypted, but we have not decided how to crypt them... Apr 29, 2009 r140 (Changed ID to int(11) auto_increment) committed by k00pa.pelikoira - Changed ID to int(11) auto_increment Changed ID to int(11) auto_increment Apr 25, 2009 issue 23 (Full PEAR integration?) commented on by possible248 - I have not used PEAR either, but a lot of other people have, and it would save some time in writing components. I have not used PEAR either, but a lot of other people have, and it would save some time in writing components. Apr 24, 2009 issue 23 (Full PEAR integration?) commented on by k00pa.pelikoira - I really don't like the PEAR I don't know why, but I have never used it... I really don't like the PEAR I don't know why, but I have never used it... Apr 24, 2009 issue 14 (APIs for things third-party developers can do anyway?) commented on by k00pa.pelikoira - Format could be <xml> or yaml or something, but I think, do we really need to write stuff to files? But I think it should be component. Everything we can do as component, lets do it as component. Format could be <xml> or yaml or something, but I think, do we really need to write stuff to files? But I think it should be component. Everything we can do as component, lets do it as component. Apr 24, 2009 r139 (Added new BURST_LOGGING_ENABLED variable so logging can be d...) committed by k00pa.pelikoira - Added new BURST_LOGGING_ENABLED variable so logging can be disabled, also modified logging function so it works. I also wan't to ask/notify ppl to develop more actively :) How about some code burst at summer? Added new BURST_LOGGING_ENABLED variable so logging can be disabled, also modified logging function so it works. I also wan't to ask/notify ppl to develop more actively :) How about some code burst at summer? Apr 24, 2009 ConfigFileParams (Documents the various parameters in the configuration file.) Wiki page edited by k00pa.pelikoira Apr 24, 2009 issue 9 (Global logging system) commented on by k00pa.pelikoira - Database erros could be put to db_errors.log file that is on secret directory so ppls can't see them. Database erros could be put to db_errors.log file that is on secret directory so ppls can't see them. Mar 27, 2009 WikiIndex (The wiki home page.) Wiki page edited by possible248 Mar 27, 2009 CodingStandard (Describes how PHP code should be formatted to be consistent ...) Wiki page added by possible248 Mar 26, 2009 r135 (Added parameter to BurstDatabase::query (). When set to tru...) committed by possible248 - Added parameter to BurstDatabase::query (). When set to true, query will be echoed before being executed. This will eventually be replaced by a more flexible deugging mode. Added parameter to BurstDatabase::query (). When set to true, query will be echoed before being executed. This will eventually be replaced by a more flexible deugging mode. Feb 27, 2009 r134 (Recovered the installer... I also added do_install.php. When...) committed by k00pa.pelikoira - Recovered the installer... I also added do_install.php. When user uses installer install.php askes questions and do_install.php will do the installion. Recovered the installer... I also added do_install.php. When user uses installer install.php askes questions and do_install.php will do the installion. Feb 20, 2009 issue 26 (Expections.php causing parser/syntax error (crit)) Status changed by possible248 - Fixed. :D Problem was that classes can't be terminated with ; Instead of writing {{{ <?php class SomeClass extends BaseClass; ?> }}} You have to write {{{ <?php class SomeClass extends BaseClass {} ?> }}} Status: Verified Fixed. :D Problem was that classes can't be terminated with ; Instead of writing {{{ <?php class SomeClass extends BaseClass; ?> }}} You have to write {{{ <?php class SomeClass extends BaseClass {} ?> }}} Status: Verified Feb 20, 2009 r133 (Fixed bug in exceptions.php) committed by possible248 - Fixed bug in exceptions.php Fixed bug in exceptions.php Feb 20, 2009 r132 (All authentications is handled by this class. (logins/logout...) committed by k00pa.pelikoira - All authentications is handled by this class. (logins/logouts/users/etc) All authentications is handled by this class. (logins/logouts/users/etc) Feb 20, 2009 r131 (Added logging database options that was missing from templat...) committed by k00pa.pelikoira - Added logging database options that was missing from template of config file. Added logging database options that was missing from template of config file. Feb 20, 2009 r130 (Modified database query to work with $BURST_LOGGING_TABLE v...) committed by k00pa.pelikoira - Modified database query to work with $BURST_LOGGING_TABLE variable. But is plain connections used? Or should we change this file to use database api and what is the api now :) Modified database query to work with $BURST_LOGGING_TABLE variable. But is plain connections used? Or should we change this file to use database api and what is the api now :) Feb 20, 2009 ConfigFileParams (Documents the various parameters in the configuration file.) Wiki page edited by k00pa.pelikoira Feb 20, 2009 issue 26 (Expections.php causing parser/syntax error (crit)) reported by k00pa.pelikoira - What steps will reproduce the problem? 1. get plain svn checkout 2. create burst_config.php 3. open index.php What is the expected output? What do you see instead? Parse error: syntax error, unexpected ';', expecting '{' in /var/www/burstcms/errors/exceptions.php on line 47 Please use labels and text to provide additional information. So this can be solved, but it isn't really working way... Removing exceptions include line from index.php (line 46 index.php) "require_once BURST_ERROR_PATH . '/exceptions.php';" So there is a problem inside expections.php. I opened that file, but I didn't found anything that could be wrong, so if possible247 could look at it and try to solve this problem. :) What steps will reproduce the problem? 1. get plain svn checkout 2. create burst_config.php 3. open index.php What is the expected output? What do you see instead? Parse error: syntax error, unexpected ';', expecting '{' in /var/www/burstcms/errors/exceptions.php on line 47 Please use labels and text to provide additional information. So this can be solved, but it isn't really working way... Removing exceptions include line from index.php (line 46 index.php) "require_once BURST_ERROR_PATH . '/exceptions.php';" So there is a problem inside expections.php. I opened that file, but I didn't found anything that could be wrong, so if possible247 could look at it and try to solve this problem. :) Feb 20, 2009 r128 (Missing ";" char added.) committed by k00pa.pelikoira - Missing ";" char added. Missing ";" char added. Feb 20, 2009 r127 (Added a cool ascii art image to README file. :-) ) committed by k00pa.pelikoira - Added a cool ascii art image to README file. :-) Added a cool ascii art image to README file. :-) Feb 12, 2009 r126 (Made some small changes. Doing a commit just so everybody kn...) committed by possible248 - Made some small changes. Doing a commit just so everybody knows we're still working. Made some small changes. Doing a commit just so everybody knows we're still working. Older Dec 25, 2008 MilestoneOne (Describes the task and the order of the tasks that should be...) Wiki page edited by possible248 Dec 21, 2008 WikiIndex (The wiki home page.) Wiki page edited by possible248 Dec 21, 2008 SqlSyntax (Describes how SQL should be written for BurstCMS) Wiki page added by possible248 Dec 20, 2008 r122 (Changelog for BurstCMS SVN revision 121: * Fixed portion...) committed by possible248 - Changelog for BurstCMS SVN revision 121: * Fixed portions of error handling inside index.php * Removed ADOdb Lite and returned to the old database layer. * Because of the change described above, the old database layer has been removed from the branches directory. * Removed 'BURST_DB_DRIVERS_PATH' as we no longer use ADOdb Lite. * Added 'database.constants.php', which contains a set of constants representing database constraints. Changelog for BurstCMS SVN revision 121: * Fixed portions of error handling inside index.php * Removed ADOdb Lite and returned to the old database layer. * Because of the change described above, the old database layer has been removed from the branches directory. * Removed 'BURST_DB_DRIVERS_PATH' as we no longer use ADOdb Lite. * Added 'database.constants.php', which contains a set of constants representing database constraints. Dec 19, 2008 r121 (Changelog for BurstCMS SVN revision 121: * Fixed portion...) committed by possible248 - Changelog for BurstCMS SVN revision 121: * Fixed portions of error handling inside index.php * Removed ADOdb Lite and returned to the old database layer. * Because of the change described above, the old database layer has been removed from the branches directory. Changelog for BurstCMS SVN revision 121: * Fixed portions of error handling inside index.php * Removed ADOdb Lite and returned to the old database layer. * Because of the change described above, the old database layer has been removed from the branches directory. Dec 07, 2008 r120 (Added the old databaes layer as a branch, so we can continue...) committed by possible248 - Added the old databaes layer as a branch, so we can continue developing it if we wish. Added the old databaes layer as a branch, so we can continue developing it if we wish. Dec 06, 2008 r119 (Changelog for BurstCMS SVN revision 119: * Finally updat...) committed by possible248 - Changelog for BurstCMS SVN revision 119: * Finally updated this change log. * Made slight modifications to the exceptions system. * Started working on a better start on the BurstCMS installer. * Updated the BurstCMS configuration file. * Removed traces of multidb support. Multidb may be brought back later. Changelog for BurstCMS SVN revision 119: * Finally updated this change log. * Made slight modifications to the exceptions system. * Started working on a better start on the BurstCMS installer. * Updated the BurstCMS configuration file. * Removed traces of multidb support. Multidb may be brought back later. Nov 26, 2008 PermissionsSystem (Describes the permissions system that BurstCMS uses) Wiki page added by possible248 Nov 23, 2008 InstallerTasks (Describes the job of the BurstCMS installer.) Wiki page edited by possible248 Nov 22, 2008 WikiIndex (The wiki home page.) Wiki page edited by k00pa.pelikoira Nov 22, 2008 UrlStructure Wiki page added by k00pa.pelikoira

issue 26 (Expections.php causing parser/syntax error (crit)) reported by k00pa.pelikoira - What steps will reproduce the problem? 1. get plain svn checkout 2. create burst_config.php 3. open index.php What is the expected output? What do you see instead? Parse error: syntax error, unexpected ';', expecting '{' in /var/www/burstcms/errors/exceptions.php on line 47 Please use labels and text to provide additional information. So this can be solved, but it isn't really working way... Removing exceptions include line from index.php (line 46 index.php) "require_once BURST_ERROR_PATH . '/exceptions.php';" So there is a problem inside expections.php. I opened that file, but I didn't found anything that could be wrong, so if possible247 could look at it and try to solve this problem. :)

What steps will reproduce the problem? 1. get plain svn checkout 2. create burst_config.php 3. open index.php What is the expected output? What do you see instead? Parse error: syntax error, unexpected ';', expecting '{' in /var/www/burstcms/errors/exceptions.php on line 47 Please use labels and text to provide additional information. So this can be solved, but it isn't really working way... Removing exceptions include line from index.php (line 46 index.php) "require_once BURST_ERROR_PATH . '/exceptions.php';" So there is a problem inside expections.php. I opened that file, but I didn't found anything that could be wrong, so if possible247 could look at it and try to solve this problem. :)

Earlier this year

Older