Call-time pass-by-reference
| Project: | Taxonomy Manager |
| Version: | 6.x-2.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hello,
After updating to version 6.x - 2.0, I get now an error message on the taxonomy manager page:
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1786
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1786
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1789
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1789
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1792
Warning: Call-time pass-by-reference has been deprecated in /is/htdocs/XXX/www/sites/all/modules/taxonomy_manager/taxonomy_manager.admin.inc on line 1792
thank you
#1
Hi!
Thanks for this report! I fixed it and committed the changes to the dev version. This happens when using the double tree interface.
#2
var annoying
#3
very annoying
#4
Thank you for the fast reaction. The actual "dev" version does not have this issue anymore.
#5
yeah, I read it
the "annoying" comment was a kind of suggestion for a minor release with the fix
sorry if it bothers you
#6
@arhak: #4 is referred to #1, not to your comments.
#7
Would you mind rolling out a quick bugfix release with this? This caught us by surprise today :-\
#8
So where is the actual dev version since you cannot download it from the project page?
#9
I see the development snapshots in the project page.
#10
Currently - as with vers. 6.x-2.0 of Taxonomy Manager , I still have the same problem.
Please roll out a new release.
#11
I think it would definitely help to roll out a quick 6.x-2.1 to fix this, it's a pretty jarring error.
#12
added new release :-)
#13
Automatically closed -- issue fixed for 2 weeks with no activity.