M8 I hate to tell you this but I think you've introduced a different prob with 2.7
| Project: | View Reference |
| Version: | 6.x-2.7 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
So yeah, the args are working really nice now with view reference fields and I'd like to switch to using it again for the pages we were discussing the other day.
But I started getting these annoying status messages on many of my pages.
It's taken me another several hours today working backwards trying to work out where these are coming from.
They occur in the same place and look the same as the standard admin status messages that inform one of certain state changes but they just contain "page_1" or nothing or some other unhelpful or unnecessary info.
See example code below. . .
page_1
I started to suspect view reference since it seemed to occur only on pages associated with view ref fields.
I stepped back to 2.6 and BINGO the unnecessary status messages are gone. . .
See the attached screenshot if this description is not enough.
I think there is also a bigger problem, when I ran cron manually with view ref 2.7 installed whatever view reference is doing with the normal drupal status messages it's going into some kind of loop. . .
I had a status message wrapped in dozens of containg divs with the green border and light green background.
Any chance this is a quick fix?
| Attachment | Size |
|---|---|
| annoyingStatus.jpg | 57.49 KB |

#1
#2
wtf
I just looked in the code I developed, and the code I uploaded to the CVS repository - there is not a single instance of drupal_set_message in there
I downloaded the file off drupal.org and it is in there.
what the hell is going on?? I should just email this module to the people who want it, because drupal.org does not seem to give you the module that I have??
#3
removed in 2.8 and I'll download it and scan the code to make sure it's not there!
#4
Thanks for a quick turn around on that one!!!
#5
Automatically closed -- issue fixed for two weeks with no activity.