|
Anonymous |
Quote:
think it is a bit
annoying
when there is a 'bug crash' in my drake
installation
... and no possibility to use my
settings/works
after this
it happend to my test
run of Drake 4.4 beta, yesterday.
( was a bug tracked and
reported before - SQLite db, admin-template-edit .. class ui.php
)
I had spent some time to customize my drake 4.4
setup.
Got the crash.
All my work lost,
because no
way but to make a new upload/install.
Not
really, you can overwrite the php files with the latest SVN
revision and it will work...but the SVN revision might have other
issues.
Quote:
There has got to be better ways
than to annoy all
testusers of Drake CMS this way.
Sure, we could
not release if not before heavy testing, but we
would probably have to pay people to test Drake CMS...and some
bugs might anyway not be spotted if not after the release
Quote:
There is
probably some easy way.
Software has bugs, if we work
hard we can remove 99% of them but there is no perfection in
software development  Quote:Because like now, I can NOT EVEN browse my Frontpage of
Drake! ... and any use of admin again is out of
question Regards  phpMaster
Using the latest SVN revision you could get back
your data in form of an SQL backup; I understand the frustration
you are experiencing...I also got that (bad) feeling many times.
This instability is something that is really annoying users, but
- trust me - it is not something that we can simply remove in a
while. We are working on the core to bring in it the necessary
modifications to have less problems in future. We are still
re-designing Drake CMS, each release is a step further into the
re-design. We are also trying to stabilize as much as we can the
latest releases, the next v0.4.5 should be very stable.
If you have ideas about how to have a stable Drake CMS in a
quicker way and without annoying our users, please say! I'd like
very much to have project management advices |
After Drake crash - no more .. 