This post can't be referenced
Tue, 10/11/2009 - 13:53
I'm having a bit of a problem with an error I've been receiving when creating a clone of an Edition: "This post can't be referenced."
I suspect the root of the problem is in Views, which has been acting strangely of late. As it happens, I have a test site that also has PP installed, and I have compared the Views settings there to the ones I'm using on my live site. I can see no discrepancies, so it must be I have missed something, apparently.
I suspect something is not communicating node references somewhere, so naturally they cannot be referenced.
I also have a second problem, which I believe is related to the first. I have "pages" that were created using my channel's terms, but those pages have stopped showing any stories on them. They used to show stories, but no longer do. Each story has a Channel reference to go with it. In most cases, Channel stories are, where appropriate, published as a reverse chronological story listing. Other Channel terms, such as "News", are set up to publish as an Edition.
My first check was in the Views area, where I checked settings for story_view. I found, however, the settings there are the same as they are in my test site. I went through each setting in the View, and settings match perfectly, as far as I have been able to determine, with my test site. So the flaw must be elsewhere else. I feel confident that one of the Views parameters somewehere else must be the source of the problem.
Any ideas?
Thu, 12/11/2009 - 09:37
#2
So, uh ... is your site back
So, uh ... is your site back to working as normal now?
Sat, 14/11/2009 - 13:13
#3
Kinda, Sorta
Well, I have a new "old" site because I kept getting a truckload of MySQL errors when trying to upgrade from version 0.18, I think it was, to 0.28. The old database couldn't handle the changes, I guess, and I had to scrap the site entirely, and build afresh.
Oddly, I had another old site, and tried the update, and it was ruined, as well. Guess you have to keep up with incremental releases and not leapfrog. I'm running PHP 5.29 and MySQL 5.0.45. But now I'm nervous, wondering if when another release of PP comes out if there'll be more MySQL trouble.
Well, I'll back up the home directory and database before I upgrade again to a new PP version, although if that is not successful, I'm not sure what I will do beyond that.
So, the answer is yes - the test site is up and running, but I hope I don't get any errors when it's time to upgrade again on my production site. Fortunately, the test site serves as a punching bag to see if an update will be successful, and that way my production site stays safe. They are on different servers.
Sorry for the long note. Guess I'm just frustrated.
Sun, 15/11/2009 - 14:05
#4
...
Hi,
No, you can't upgrade from 0.18 directly to 0.28. For each release I make, I specify what versions can be upgraded to it. For example, to upgrade to 0.28, you must only upgrade from 0.25 or later. I explicitly say this in the release notes.
I do admit it is a hassle to have so many frequent upgrades, but there's not much I can do about it. Drupal is very security conscious and completely open and transparent about potential vulnerabilities. Hence, there are (comparatively) frequent security announcements (even though many of them are not usually exploitable unless you have an unusual configuration). In order to not unnecessarily alarm ProsePoint users, I patch every security vulnerability, regardless of whether it actually affects ProsePoint.
The alternative is to keep quiet about vulnerabilities and blindly hope malicious people don't use them to attack ProsePoint sites - which I don't think is a realistic option at all. Unfortunately, if you want to run a website, you need to keep the site patched.
Another good practice is always to backup before you attempt an upgrade. This is strongly recommended (although I expect many people aren't this diligent for whatever reason).
Mon, 16/11/2009 - 13:47
#5
For those who are reading this
For those who are reading this, then, I guess the lesson is that if they have a, say 0.13 version of PP, is to climb the ladder to 0.14, to 0.15, then to 0.16, then so on until they reach 0.28 rather than to jump from 0.13 to 0.28.
That would seem to be the path, but of course it would take a long time to do that. The lesson here is to either keep your old version (not advisable), or keep up with the updates (preferred). Otherwise, your database will be wrecked.
Mon, 16/11/2009 - 15:54
#6
Yes, but I should offer a
Yes, but I should offer a slight correction. Depending on the changes for each release, sometimes you can jump releases. For example, it is possible to go 0.15 => 0.21 => 0.25 => 0.28. It's all specified in the release notes (though maybe it could be a bit clearer).
Sat, 01/05/2010 - 05:59
#7
how to edit story_view
hi, there. i'm new to ProsePoint and Drupal. i'm having a similar "Headlines: this post can't be referenced" error when i try to generate a new Edition of channel using Headlines that are not yet Public. i wanted to try to tinker with your solution you posted but i'm a little lost as to where to find the path that you've listed. i'm at a loss for where to find the story_view to edit. thanks for your help!
Sat, 01/05/2010 - 10:25
#8
recommend you create a new thread where I'll help you diagnose
Hi,
Firstly, if you've never edited story_view, then your error message "this post can't be referenced" is not caused by it and I'd recommend you create a new thread where I'll help you diagnose it.
Editing story_view is something only advanced users should do because it uses Drupal's Views module and if you make a mistake, your site could very well break (which is what the original poster experienced).
If you really really want to have a look at story_view, you need to enable the module Views UI on .../admin/build/modules, then visit Administer // Site Building // Views.
But you have been warned to be careful :)
Sat, 01/05/2010 - 13:19
#9
separate thread regarding "this post can't be referenced error"
since i'm a beginner user, i'd rather not tinker with advanced editing. i've created a separate post describing the issue at: http://www.prosepoint.org/node/759
thank you!
The problem was in the story_view area.
Under defaults > filters > node type > story, the subselection was set to "Edition" instead of "Story."
Something so small can cause major grief. Oh well, that's the life of a Drupal detective.