Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi! im new to drupal. this is my 2nd post This is the error that shows on screen after upgrading/updating tribune module: h
[[[[[[[[[[[[[[[ * warning: pg_query() [function.pg-query]: Query failed: ERROR: operator does not exist: character varying > integer LINE 2: ...ROM drupal_tribune WHERE drupal_tribune.post_time > 0 AND la... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. in \www\includes\database.pgsql.inc on line 139.
* user warning: query: SELECT * FROM drupal_tribune WHERE drupal_tribune.post_time > 0 AND last_modified <= 1272080134 ORDER BY post_id DESC LIMIT 10 in \www\modules\tribune\tribune.module on line 730. ]]]]]]]]]]]]]]]]]
I tried uninstalling first the previous version tribune-6.x-1.1 because of a new update 6.x-1.1 detected in cron.
steps i did in modules: uncheck, save, uninstall, update.php, delete file 6.x-11, paste new 6.x-1.2, check, save, update.php
no errors found after update.php, but if i go to other pages i see d above errors... btw im using WAPP, is this because of postgre? i never had errors w/ the previous tribune version. if anyone can assist, thanks!!!
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | tribune white text.jpg | 41.63 KB | mechdrupal |
Comments
Comment #1
SeeSchloss commentedWait, are you talking about versions 1.1, 1.11, 1.2 or 1.12?
There is no update (in update.php) for going from 1.11 to 1.12 (the two latest versions), so I don't know how this could happen. On the other hand... I can't see why you would be updating from 1.1 to 1.2 since it is so old, so maybe you are updating from 1.1 to 1.12?
In any case, I understand where this problem comes from, I have just fixed it in CVS and am going to make a bugfix release soon, that will be Tribune 1.13
Comment #2
mechdrupal commentedSorry for putting a wrong version 1.2 in filing. wrong drop down list selection, sorry again!
wow thanks for the fast reply. actually its from 6.x-1.11 to 6.x-1.12.
i think this has something to do with database migration? w/c i read from other threads. is it bcoz im using Postgre as my DB WAPP? majority of the developers use WAMP MySql codes. =)
the other reason why i really upgraded is because 6.x-1.11 block menu long chat box OVERLAPS my frontpage(graphical bug somethin') for most users, except when im logged in as admin account... duno the reason. im using acquia slate theme.
so what i did after the above DB query error message came-out, i switched back/restored my old 1.11 version. and no errors came-out but still has some graphical issues w/ the chat box.
anyways, if this can't be solved, it leaves mo no choice but to wait for 1.13. =) tribune is still great despite some minor bugs. cheers!
Comment #3
SeeSchloss commentedWell it doesn't have to do with database migration actually, by error in 1.12 I simply replaced a '0' with 0 in some place, and PostgreSQL doesn't like it although MySQL didn't tell me anything :)
I'm using LAMP by the way... not WAMP :P I have another dev install using Postgre but since I didn't even think I had changed anything regarding the database, I didn't run tests on it.
As for the long input, it will be fixed in the next release. Drupal sets a default 'size' attribute that is a bit big for a block, so now I unset it.
I'll probably release 1.13 just later today, once I've fixed a few other things.
Comment #4
mechdrupal commentedWow congrats!
Just wanna inform you, thought this might help in your development of tribune.
1.) you really did great with postgre error message thing... very cool. no error found from upgrading 1.11 to 1.13.
2.) no overlapping of chatbox to center of page, the way it did before.
& lastly,
3.)i think the turning white of all text is still there =p but for me, its just a minor glitch anyway...
OVERALL: i'd say Tribune is COOL! thumbs up. Many thanks for this module...
Comment #5
SeeSchloss commentedHmm, can you tell me more about your third point?
That doesn't sound like it's the same bug I fixed (what I fixed was only the background color of the textfield), maybe it's something I haven't noticed yet or something I have forgotten.
Comment #6
mechdrupal commentedattached here is the printscreen for you to see and check... hope this helps. More power to tribune!