Upgrading to 3.1.9 appears to loose helper custom code #965
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#965
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce the issue
Using JCB tag 3.1.8,
in Libs & Helpers -> Add PHP (helper Classes - Both admin & site)
Enter custom code (I had entered close to 9000 lines at the point this issue happened)
Install JCB tag 3.1.9
Compile the component
Expected result
Code should compile and custom helper code (both admin & site) should be visible in the GUI and in the helper php file.
Actual result
All code within the "/[JCBGUI.joomla_component.php_helper_both.26.$$$$]/" tags is gone, and the entry area within the GUI is blank.
System information (as much as possible)
Additional comments
After recovering the lost code from an archive and entering it back in and re-compiling it works fine.
Upgraded to 3.1.12 and re-compile and everything is fine.
Not sure how this could have happened, but rather concerning to loose about 9,000 lines of code on a compile after an upgrade.
Wondering if anyone else has seen anything like this - or if there are any cautions posted anywhere when upgrading to a newer tag version (other than back everything up before hand)?
NOTE: I have not had a chance to test this on any other install to see if it was limited to this specific instance but will try to do that in the next day or two.
Never seen this happen...
OK ... I will hopefully have time to upgrade one of my other JCB dev sites this coming week to see if this is repeatable. If not I'll just close this as some anomoly.
NOTE: I'm using PHP Storm as an IDE and have noticed some other peculiarities since the latest version came out. Might be possible it is related to that upgrade instead.
I'll update here within the next week to try to reproduce or close this one.
I've not been able to reproduce this on any other site so I'm just going to close this.