Do you see the view if it you enable views UI? The view shows up for me, and it would be really strange if it would stop showing up completely since it's in code. The view shows up as it should in my install.
From which version to which version did you upgrade?
Finally, go to /admin/settings/performance and clear the cache, just to make sure that nothing like that causes issues.
The only difference between 1.3 and 1.4 were a few module upgrades, among them webform which was a security update. We did no changes to the configuration in this release.
I went from NS 6x1.1 to 6x1.2 as per the updates screen showing the recommended version of 1.2, but it appears that we are up to 1.4 now? That is odd. Anyway, I hit the download link from the Available Updates screen and was only presented with ns_core to download, so that is all that I updated. Since then I was looking at the project site and noticed that we are up to 1.4 with a full D6 install. I will try the full core update and see if that fixes the issue.
On my non-production site I did roll back to 1.1 and it came back, so if I have to I can fall back to that at least.
I performed a total code update and now everything is back to where it was, (still had to update Views RSS) so that is good, but there is something that confuses me.
In Available Updates it shows as NodeStream Core 6.x 1.2 but I uploaded 6x-1.4 dated 11-Mar-2012. I would have expected that when you do a total code update (updated using the whole package including Drupal 6.25) that the current code level would have shown. It also shows 6x-1.2 in admin/modules. The only directories that I did not overwrite was /profiles/nodestream/themes, /sites/all and /sites/default.
I will concede that I probably should have not used the link in the Available Updates page and went directly to the project site, but I think that this is the first time that I have taken an incomplete update from the link available in AU. I am unsure who is responsible for that, but it would be nice if that were fixed. Before I uploaded the patch previously, I did look in the Read Me and it was blank, so I found that odd as well.
Running update on production now. Thanks for the very rapid response.
Comments
Hi! Do you see the view if it
Hi!
Do you see the view if it you enable views UI? The view shows up for me, and it would be really strange if it would stop showing up completely since it's in code. The view shows up as it should in my install.
From which version to which version did you upgrade?
Finally, go to /admin/settings/performance and clear the cache, just to make sure that nothing like that causes issues.
//Fabian Sörqvist
The only difference between
The only difference between 1.3 and 1.4 were a few module upgrades, among them webform which was a security update. We did no changes to the configuration in this release.
//Fabian Sörqvist
I went from NS 6x1.1 to 6x1.2
I went from NS 6x1.1 to 6x1.2 as per the updates screen showing the recommended version of 1.2, but it appears that we are up to 1.4 now? That is odd. Anyway, I hit the download link from the Available Updates screen and was only presented with ns_core to download, so that is all that I updated. Since then I was looking at the project site and noticed that we are up to 1.4 with a full D6 install. I will try the full core update and see if that fixes the issue.
On my non-production site I did roll back to 1.1 and it came back, so if I have to I can fall back to that at least.
Trying update now, will advise,
Ok, back in business, but...
I performed a total code update and now everything is back to where it was, (still had to update Views RSS) so that is good, but there is something that confuses me.
In Available Updates it shows as NodeStream Core 6.x 1.2 but I uploaded 6x-1.4 dated 11-Mar-2012. I would have expected that when you do a total code update (updated using the whole package including Drupal 6.25) that the current code level would have shown. It also shows 6x-1.2 in admin/modules. The only directories that I did not overwrite was /profiles/nodestream/themes, /sites/all and /sites/default.
I will concede that I probably should have not used the link in the Available Updates page and went directly to the project site, but I think that this is the first time that I have taken an incomplete update from the link available in AU. I am unsure who is responsible for that, but it would be nice if that were fixed. Before I uploaded the patch previously, I did look in the Read Me and it was blank, so I found that odd as well.
Running update on production now. Thanks for the very rapid response.