Blocks gone
nick123pig - January 5, 2009 - 03:43
| Project: | DrupalIt |
| Version: | 6.x-1.4-beta2 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
When I updated to 6.x-1.4-beta2, all of the drupalit blocks were gone.

#1
Also, VotingAPI shows up as required module now
#2
- The Drupalit blocks are gone.
- There is the need for another module.
- The SQL database is suddenly showing loads of errors.
Should have followed the rule "Never change a running system!" Oh well, shit happenes.
It is still a very cool module! Went back to the old version again and am seriously considering disabling the update function.
Paul.
#3
We implement drupalit with Voting API in order to have Views support.
From now on, you can made blocks via Views, so i removed the exisiting blocks.
@paul_constantine
What type of SQL Errors?
#4
This is what I get after I upload the new Drupalit module and run update.php:
* user warning: Duplicate column name 'daily_votes' query: ALTER TABLE drupalit_votes ADD daily_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'daily_first_vote' query: ALTER TABLE drupalit_votes ADD daily_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'weekly_votes' query: ALTER TABLE drupalit_votes ADD weekly_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'weekly_first_vote' query: ALTER TABLE drupalit_votes ADD weekly_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'monthly_votes' query: ALTER TABLE drupalit_votes ADD monthly_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'monthly_first_vote' query: ALTER TABLE drupalit_votes ADD monthly_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'daily_votes' query: ALTER TABLE drupalit_user_to_vote ADD daily_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'daily_first_vote' query: ALTER TABLE drupalit_user_to_vote ADD daily_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'weekly_votes' query: ALTER TABLE drupalit_user_to_vote ADD weekly_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'weekly_first_vote' query: ALTER TABLE drupalit_user_to_vote ADD weekly_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'monthly_votes' query: ALTER TABLE drupalit_user_to_vote ADD monthly_votes int(10) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
* user warning: Duplicate column name 'monthly_first_vote' query: ALTER TABLE drupalit_user_to_vote ADD monthly_first_vote int(11) in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 69.
Followed by
The following queries were executed
drupalit module
Update #1
* Failed: ALTER TABLE {drupalit_votes} ADD daily_votes int(10)
* ALTER TABLE {drupalit_votes} ALTER daily_votes SET default 0
* Failed: ALTER TABLE {drupalit_votes} ADD daily_first_vote int(11)
* Failed: ALTER TABLE {drupalit_votes} ADD weekly_votes int(10)
* ALTER TABLE {drupalit_votes} ALTER weekly_votes SET default 0
* Failed: ALTER TABLE {drupalit_votes} ADD weekly_first_vote int(11)
* Failed: ALTER TABLE {drupalit_votes} ADD monthly_votes int(10)
* ALTER TABLE {drupalit_votes} ALTER monthly_votes SET default 0
* Failed: ALTER TABLE {drupalit_votes} ADD monthly_first_vote int(11)
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD daily_votes int(10)
* ALTER TABLE {drupalit_user_to_vote} ALTER daily_votes SET default 0
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD daily_first_vote int(11)
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD weekly_votes int(10)
* ALTER TABLE {drupalit_user_to_vote} ALTER weekly_votes SET default 0
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD weekly_first_vote int(11)
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD monthly_votes int(10)
* ALTER TABLE {drupalit_user_to_vote} ALTER monthly_votes SET default 0
* Failed: ALTER TABLE {drupalit_user_to_vote} ADD monthly_first_vote int(11)
I looked into the Views module to get my Drupalit block back.
But after activating the voting API I get some ugly navigation (where I don't want it) with things like 5-Star (?) or Plus1 (??) which I don't even have on my site ... but I don't get my Drupalit "Drupal Hottest" Block back.
Could you please point out how to get the same look and feel back as before the update?
Kind Regards,
Paul.
P.S. Just got a new one:
warning: array_pop(): The argument should be an array in /srv/www/vhosts/zooot.de/httpdocs/update.php on line 315.
#5
1. I dont know why the module, run at update.php, because i haven't changed anything at the database schema.
Because of your error, i enabled the module, in a new clean installation of drupal, and i updated Drupalit, on a existing setup. Then i run update.php in both cases, and nothing changed for Drupalit.
2.
The pages of 5-Star/Plus1 are default on Voting API. Of course you could disabled them.
On Views you chose either a block or a page. And on Relationships box, you enable Node: Voting results. Then on Fields Box, you add Voting API results: Value and you choose the Drupalit View, on Appearance select.. For a block you can add Node title and that's all.
#6
Thank you for your fast reply.
I tried it the way you pointed out. The SQL errors are gone for now. That is the good news.
But the new block now breaks my layout. For one thing it is in a table that does not really look very good and for another thing the sorting does not work (even if set to the "value" column). Or it displays "next page" links (even if set to "no") , or if set to anything else than a table it does not appear at all. And each update takes half a minute. (I know, I need to change my provider badly.)
After trying this out for two days and not getting it right (I am not a developer) I will revert back to the old version and just change the info file in order to avoid the annoying error messages on my status report.
Thank you anyway for your patience and your help,
Paul.
#7
ΟΚ!
Ι am going to release Drupalit 1.4.3 with the blocks included.
#8
Great. The blocks are a key reason I was gonna use Drupalit over some of the others.
Cheers.
#9
Looking forward for the release of Drupalit 1.4.3 with the blocks included! :)
Thanks in advance! Great module.
#10
You can check the .dev version now. I have implemented better Views2 support and i added the blocks.
Please test it, and provide some feedback.
Thanks apanag.
#11
I can't seem to make the votes go on the top, highest votes from votingAPI should cause items to be descending, from most votes to least votes. But that doesnt work in Views.
#12
I just fixed the issue and update the code in .dev.