Upgrade from 5.x-1.2 to 5.x-1.3 messes up block display
bestknight - February 22, 2008 - 11:10
| Project: | Views Alpha Pager |
| Version: | 5.x-1.3 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
After upgrading to 5.x-1.3 it messed up the display of blocks in the content area.
I have a number of blocks showing up for different roles and depending on the content type using arguments. For example block1 only shows for content type A and role Alpha whereas block2 only shows for content type A and role Beta, block3 only shows for content type B and role Alpha etc. Some blocks' title gets displayed without the content area of the block (nothing should really be displayed at all as not all blocks are relevant to all content types or all roles).
Replaced 5.x-1.3 files with those of the 5.x-1.2 release and problem stopped. Do I need to do anything else (maybe with the database)?
#1
Did you run update.php after upgrading the module?
#2
From what I noted down during upgrade, yes.
Is there a way to check this, in the database tables?
#3
just visit yoursite.com/update.php, and follow the instructions. If you expand the fieldset for the modules and VFS has a number in it, then you need to apply the update.
#4
Views Alpha Pager is not even listed on the update.php page. (What is the "VFS" you've mentioned?)
As already noted, I have deleted the files of the 5.x-1.3 release and replaced these with the files of the 5.x-1.2 release. Does this makes a difference to whether the update should be shown or not? But the Views Alpha Pager is not listed at update.php even though enabled as a module (5.x-1.2 release).
#5
Tried the upgrade again (on a copy of the website) from 5.x-1.2 to 5.x-1.3 (sure to run update.php this time) and the same problem occurs. Isn't anybody else experiencing this?
#6
Sorry, I mentioned VFS which is one of my other modules (views_fastsearch) and I should have mentioned VAP (views_alpha_pager).
views_alpha_pager should be on the update.php after clicking the "run database upgrade script" link, then click the "select versions" fieldset link. If it's not there, then you don't have the 5.x-1.3 version installed.
#7
:) Thanks for your reply. It seems that the developers figured this out as the problem for me is resolved on upgrading to the 5.x-1.4 release of the module.
Marking as fixed.
#8
Automatically closed -- issue fixed for two weeks with no activity.