Deleting Pages Bug (5.7)
Permalink
This is a major bug.
If the parent page is an External Link and it has child pages that are of ANY page type. The child pages get auto-deleted instead of MOVING to the root level of the sitemap IF the External Link parent page is DELETED.
I've tried my best to be patient with 5.7 since Release and I am highly disappointed at what c5 has become.
As for backups, yes I have them and I can restore which is fine but still, this shouldn't be an issue to begin with.
If the parent page is an External Link and it has child pages that are of ANY page type. The child pages get auto-deleted instead of MOVING to the root level of the sitemap IF the External Link parent page is DELETED.
I've tried my best to be patient with 5.7 since Release and I am highly disappointed at what c5 has become.
As for backups, yes I have them and I can restore which is fine but still, this shouldn't be an issue to begin with.
MarvenMedia wrote: I am highly disappointed at what c5 has become.
So am I, because 5.7, even in version 5.7.4.2, is so full of bugs, that I must say, it ist not useable. 5.6 was a good, stable and easy to use CMS.
So am I, because 5.7, even in version 5.7.4.2, is so full of bugs, that I must say, it ist not useable. 5.6 was a good, stable and easy to use CMS.
@TorstenKelsch
You have also posted in another thread regarding 5.7 being "full of bugs".
Since the release date of 5.7, you commented on a topic about the database backup feature (not a bug) and created a topic relating to stacks (not a confirmed bug).
https://www.concrete5.org/community/forums/customizing_c5/edited-blo...
https://www.concrete5.org/community/forums/5-7-discussion/database-b...
Did you report the stack refresh issue you were having to the bug tracker?
No one can address your issues if you do not list the specific details of what they are and the steps to recreate them. The core team and core contributors do not have the time or resources to read every comment posted on the forum, because of this the bug tracker was created. If you (or others) choose not to use the bug tracker, then you can have no expectation that a potential bug will be fixed.
As a free open source project, we all can participate in improving and refining concrete5, but only if we work together.
You have also posted in another thread regarding 5.7 being "full of bugs".
Since the release date of 5.7, you commented on a topic about the database backup feature (not a bug) and created a topic relating to stacks (not a confirmed bug).
https://www.concrete5.org/community/forums/customizing_c5/edited-blo...
https://www.concrete5.org/community/forums/5-7-discussion/database-b...
Did you report the stack refresh issue you were having to the bug tracker?
No one can address your issues if you do not list the specific details of what they are and the steps to recreate them. The core team and core contributors do not have the time or resources to read every comment posted on the forum, because of this the bug tracker was created. If you (or others) choose not to use the bug tracker, then you can have no expectation that a potential bug will be fixed.
As a free open source project, we all can participate in improving and refining concrete5, but only if we work together.
@MrKDilkington:
I cannot remember all the issues I ran into, but in the meantime I am highly satisfied (concrete5.7.5.2 and concrete5.7.5.3).
And yes, you are right, I should have reported in the bug tracker.
I cannot remember all the issues I ran into, but in the meantime I am highly satisfied (concrete5.7.5.2 and concrete5.7.5.3).
And yes, you are right, I should have reported in the bug tracker.
I recommend posting to the bug tracker and to the GitHub issues page.
https://www.concrete5.org/developers/bugs/5-7-3-1/...
https://github.com/concrete5/concrete5-5.7.0/issues...
Otherwise the core team will not be aware of or able to address the problem.