BEdita

Today we release a new online resource dedicated to BEdita documentation: docs.bedita.com Here we are collecting many technical articles, it will be the official technical documentation reference. It's still a beta, many features are missing, but ... [More] we are working on them. Suggestions and feedback are highly appreciated: you may use the newly created BEdita google group to let us know what you think.   [Less]

Today we release a new online resource dedicated to BEdita documentation: docs.bedita.com Here we are collecting many technical articles, it will be the official technical documentation reference. It's still a beta, many features are missing, but ... [More] we are working on them. Suggestions and feedback are highly appreciated: you may use the newly created BEdita google group to let us know what you think.   [Less]

Today we release a new online resource dedicated to BEdita documentation: docs.bedita.com Here we are collecting many technical articles, it will be the official technical documentation reference. It's still a beta, many features are missing, but we ... [More] are working on them. Suggestions and feedback are highly appreciated: you may use the newly created BEdita google group to let us know what you think.   [Less]

BEdita 3.1.6 stable codename "ulmus" releasedBecause of some issues with Firefox 11 and TinyMCE 3.3 used in BEdita 3.1.5 we have upgraded TinyMCE to 3.4.9 and we announce today BEdita 3.1.6 stable*. The issue was reported on the new BEdita support at ... [More] https://groups.google.com/forum/?fromgroups#!topic/bedita/MQ0M3jnODEc We highly reccomend to upgrade BEdita to 3.1.6 version as soon as possible. This is the sixth bugfix release for BEdita 3.1 “Ulmus”*. Changes include: upgrade to tinyMCE 3.4.9 due to issues with Firefox 11 and multinstance of tinyMCE other minor bugfix See changelog for all changes. Explore and follow BEdita also on: https://groups.google.com/forum/?fromgroups#!forum/bedita - official support on Google Groups api.bedita.com - API and documentation sourceforge.net/projects/bedita - SF project page (also on Freshmeat, Ohloh, Facebook, Twitter)   (*) “ulmus” : [ pronounce /ˈəl-məs ] aka elm, a tall deciduous tree that typically has rough serrated leaves and propagates from root suckers, Genus Ulmus, family Ulmaceae. [Less]

BEdita 3.1.6 stable codename "ulmus" releasedBecause of some issues with Firefox 11 and TinyMCE 3.3 used in BEdita 3.1.5 we have upgraded TinyMCE to 3.4.9 and we announce today BEdita 3.1.6 stable*. The issue was reported on the new BEdita support ... [More] at https://groups.google.com/forum/?fromgroups#!topic/bedita/MQ0M3jnODEc We highly reccomend to upgrade BEdita to 3.1.6 version as soon as possible. This is the sixth bugfix release for BEdita 3.1 “Ulmus”*. Changes include: upgrade to tinyMCE 3.4.9 due to issues with Firefox 11 and multinstance of tinyMCE other minor bugfix See changelog for all changes. Explore and follow BEdita also on: https://groups.google.com/forum/?fromgroups#!forum/bedita - official support on Google Groups api.bedita.com - API and documentation sourceforge.net/projects/bedita - SF project page (also on Freshmeat, Ohloh, Facebook, Twitter)   (*) “ulmus” : [ pronounce /ˈəl-məs ] aka elm, a tall deciduous tree that typically has rough serrated leaves and propagates from root suckers, Genus Ulmus, family Ulmaceae. [Less]

BEdita 3.1.6 stable codename "ulmus" releasedBecause of some issues with Firefox 11 and TinyMCE 3.3 used in BEdita 3.1.5 we have upgraded TinyMCE to 3.4.9 and we announce today BEdita 3.1.6 stable*. The issue was reported on the new BEdita support ... [More] at https://groups.google.com/forum/?fromgroups#!topic/bedita/MQ0M3jnODEc We highly reccomend to upgrade BEdita to 3.1.6 version as soon as possible. This is the sixth bugfix release for BEdita 3.1 “Ulmus”*. Changes include: upgrade to tinyMCE 3.4.9 due to issues with Firefox 11 and multinstance of tinyMCE other minor bugfix See changelog for all changes. Explore and follow BEdita also on: https://groups.google.com/forum/?fromgroups#!forum/bedita - official support on Google Groups api.bedita.com - API and documentation sourceforge.net/projects/bedita - SF project page (also on Freshmeat, Ohloh, Facebook, Twitter)   (*) “ulmus” : [ pronounce /ˈəl-məs ] aka elm, a tall deciduous tree that typically has rough serrated leaves and propagates from root suckers, Genus Ulmus, family Ulmaceae. [Less]

BEdita 3.1.6 stable codename "ulmus" releasedBecause of some issues with Firefox 11 and TinyMCE 3.3 used in BEdita 3.1.5 we have upgraded TinyMCE to 3.4.9 and we announce today BEdita 3.1.6 stable*. The issue was reported on the new BEdita support at ... [More] https://groups.google.com/forum/?fromgroups#!topic/bedita/MQ0M3jnODEc We highly reccomend to upgrade BEdita to 3.1.6 version as soon as possible. This is the sixth bugfix release for BEdita 3.1 “Ulmus”*. Changes include: upgrade to tinyMCE 3.4.9 due to issues with Firefox 11 and multinstance of tinyMCE other minor bugfix See changelog for all changes. Explore and follow BEdita also on: https://groups.google.com/forum/?fromgroups#!forum/bedita - official support on Google Groups api.bedita.com - API and documentation sourceforge.net/projects/bedita - SF project page (also on Freshmeat, Ohloh, Facebook, Twitter)   (*) “ulmus” : [ pronounce /ˈəl-məs ] aka elm, a tall deciduous tree that typically has rough serrated leaves and propagates from root suckers, Genus Ulmus, family Ulmaceae. [Less]

4 simple steps to follow if your BEdita applications are not workingIt happens: your application is not responding, you may have a blank page, some elements are not displayed, page layout is broken, you get mysterious error messages.....but you don't ... [More] know what's going wrong and how to fix it. Ok, don't panic :-) Here simple checklist in four steps to use in similar situations: debug level - core.php - it's a common practice to set a debug level during development/testing of your application, you do so by setting Configure::write('debug', 1); in bedita-app/config/core.php in backend or in frontends/[frontend-name]/config/core.php in your specific [frontend-name] frontend. It may help: additional information should be displayed in your browser and in log files. Remember to remove debug level by setting Configure::write('debug', 0) for a production system. view BEdita log files - backend log files are in bedita-app/tmp/logs folder for backend and in frontends/[frontend-name]/tmp/logs for your [frontend-name] frontend. Look at error.log file first, then view debug.log view web servers log files - if you're using Apache usually these files are located in a common log directory for your web server, but you can specify other custom log directories for both backend and frontend. In typical Unix setup you may find these files in /var/log/apache2/ (without custom log directories). Read error.log first, then look at access.log. get online support - if the problem is still obscure even after a web search, let's write to our google group to get support     [Less]

4 simple steps to follow if your BEdita applications are not workingYour application is not responding, you have a blank page, some elements are not displayed, page layout is broken, you get mysterious error messages.....but you don't know what's ... [More] going wrong and how to fix it? Ok, don't panic :-) Here a simple checklist in four steps to use in such situations: debug level - core.php - it's a common practice to set a debug level during development/testing of your application, you do so by setting Configure::write('debug', 1); in bedita-app/config/core.php in backend or in frontends/[frontend-name]/config/core.php in your specific [frontend-name] frontend. It may help: additional information should be displayed in your browser and in log files. Remember to remove debug level by setting Configure::write('debug', 0) for a production system. view BEdita log files - backend log files are in bedita-app/tmp/logs folder for backend and in frontends/[frontend-name]/tmp/logs for your [frontend-name] frontend. Look at error.log file first, then view debug.log view web servers log files - if you're using Apache usually these files are located in a common log directory for your web server, but you can specify other custom log directories for both backend and frontend. In typical Unix setup you may find these files in /var/log/apache2/ (without custom log directories). Read error.log first, then look at access.log. get online support - if the problem is still obscure, write to our google group to get support     [Less]

After several issues with the bulletin board we have decided to move BEdita support on Google Groups at https://groups.google.com/group/beditaWe think it will be a better place to help you. Our hope is to involve more people around the project and ... [More] try to build a great community.The forum's pages will remain in readonly mode to allow users to consult the discussions already present.See you soon in the new support pages athttps://groups.google.com/group/bedita [Less]