Posted by VladSavitsky on June 20, 2008 at 4:13pm
| Project: | Tagadelic |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I have found in logs that path tagadelic/chunk/images/x.gif gives a warning:
implode() [function.implode]: Argument to implode must be an array. в файле /home/..../sites/all/modules/tagadelic-6.x-1.0/tagadelic.module в строке 212.
To fix this change:
function tagadelic_get_weighted_tags($vids, $steps = 6, $size = 60) {
//Fixing a bug with wrong path. Start
if (!is_array($vids)) $vids=array();
//Fixing a bug with wrong path. End
Comments
#1
My opinion here is just return an array() instead of $vids = array();
Why should we read from the cache wrong data?
<?phpfunction tagadelic_get_weighted_tags($vids, $steps = 6, $size = 60) {
if (!is_array($vids)) {
return array();
}
// ...
?>
#2
Here is my patch.
It against module's HEAD.
#3
Can someone please test this patch?
I like its concept, and like the solution, but need at least one more person to confirm it works and does not break his/her site.
#4
I didn't apply the patch, but made the code change and now receive a "Page Not Found" error, which is acceptable since no tags exist yet.
#5
You should clear the cache IMHO.
#6
if cache is causing this, then we need to implement this in the patch: we should clear the cahce in hook_update, in that case.
#7
patch should implement a cache wipe in the update, else people get warnings.
#8
I am seeing a similar error in v5:
Message implode() [<a href='function.implode'>function.implode</a>]: Argument must be an array in /home/..../modules/tagadelic/tagadelic.module on line 208.#9
I'm interested in getting a fix against D5 but has this ever been fixed against either D6 or D5?
#10
IMO we should travers up the calling functions and fix it in the first place: simply make sure we never call the function tagadelic_get_weighted_tags without an array if vids!
#11
Subscribing
#12
Any action to address this issue?
#13
@jorgemare instead of subscribing and spamming us with updates, you could actually do somthing about it :)
@rdesantos: see #10. Maybe you can address it?
#14
@Ber Kessels: If I had the necessary knowledge or skills I'd be happy to do so. Unfortunately I don't think I do. My question was an inquiry on the status and that's all.
#15
Closing "needs work" that has been open for a long time, without anyone working on it.
#16