Hello,
An update on the issue:
Trevor has fixed the bug in the source code.
I expect to release an 1.0.4 beta within the next 2 weeks which will contain this fix and several other fixes reported.
If it's an urgent issue i can also compile a custom 1.0.3 package for you so you can apply it right now. (so please let me know if it's needed or if 2 weeks wait is fine)
Regards,
Marco
@marco , thanks for this. Do you think it is suitable to upgrade to 1.0.4 beta? Or should we wait for the final release. I kinda need to use this feature now. Currently the domains are created in Standard Primary mode which doesnt synchronize across our DNS servers. Thanks.
If it's needed now you can just manually update to 1.0.4 now.
1.0.4 code is pretty stable but some things like SQL update query needs a little fine tuning at this point (so it might pop up a warning when executing but nothing that will cause any damage or issues to your solidcp database).
@marco , I upgraded to 1.1.1 and tested the sub domain feature.
- The sub domain actually gets created as a new zone which is GREAT! (so this part works)
- Within the parent domain a secondary object is created (much like the one I reported in the first post.
I then proceeded to try to delete the sub domain, and whilst the zone was deleted, this secondary object was not deleted.
Is there a setting that needs to be activated to stop this secondary object from being created?
Thanks.
