We are very happy to announce that the SiteSupra (www.sitesupra.org) is now available for download as an open source, free, GPL-licensed CMS. We are excited that after more than ten years of work we can release it as a free and open source product and hope it will allow you to build sites fast, and win more clients because of the elegant CMS.
We anticipate contributors to become the powerful force behind improvements to the platform. We welcome feedback and contributions from developers to enrich the product with widgets and modules, and so we need your views on required components.
Contributions are highly welcome on Github - for start, you can use https://github.com/sitesupra/sitesupra-demo, which provides base demo environment to get used with SiteSupra. All new widgets, blocks and example themes should be developed there, but if you wish to alter SiteSupra core itself - please direct your pull requests to https://github.com/sitesupra/sitesupra, which holds the core of the framework.
I actually do not understand the issue the you’re having, especially “I don’t think I’ve ever
had such a problem setting up a project using a official release…” after the assets went just fine.
Could you please provide some details?
Also we’ve just noticed that our CMS user manual had a wrong URL address to the CMS backend (http://sitesupra-docs.readthedocs.org/en/latest/cms/user_manual.html) so we fixed that immediately. Maybe you meant that?
If you look at the terminal pics that I posted there seem to have been some issues with running both the database and asset set-up commands. Specifically, the line ATTENTION: This operation should not be executed in a production environment and the no x folder founds for the asset publish command. Are these not issues because they sure seem like it.
Hi, the ATTENTION line you refer to is Doctrine’s message. This is not an error message but a reminder. Same applies to the second issues - this isn’t an error. You can use the package with no problem.