I have a problem with a site that I'm working on at the moment. It started as a 6.1.5 site, and then got updated to 6.1.6 when that was released. Now it looks like something in the database is causing the publish at functionality not to work.
If I set the value for publish at for a document, it never publishes, and nothing is logged in the error log to say that anything went wrong.
However, if I switch the database connection to a different 6.1.6 install, I can publish at with content from that database quite happily. This leads me to believe that it's something in the database rather than something in my install.
I can't figure out how the auto publishing works from looking at the source, so my question is, does anyone know what (if anything) in the DB might cause the auto publish to fail? Or can anyone point me to where I should be looking in the source for the auto publish functionality?
Hi sir, a couple of things to check: Do you have any Umbraco events that might block the publish based upon a property value? Was the item valid for being published, i.e. any mandatory fields not complete? (basic I know but worth checking).
@Arie, I already tried a fresh 6.1.6 install and it was fine, so definitely not specific to 6.1.6. @Kieron, checked both of those, not an issue. I seem to have fixed it by rebuilding all of the Examine Indexes. I think there must have been something wrong with one of the indexes that's used by the system....... I'm going to do a bit more digging over the weekend to see if I can find out exactly what happened!
That's interesting. Why would the autopublish rely on the indexing? You'd expect the two to be independent processes or at the very least the failure of the indexing not to prevent the publishing of the content. But a corrupt index would fit the picture given that it's not failing on a default install.
Some of the v6 services and methods hit the Examine caches first, and then the database, I'm wondering if this is one of those? I haven't got too far into it, as I've fixed the immediate problem for now, but I'm going to delve into this further, as we've had a few issues on dev sites relating to the internal indexes recently, and I want to see if it's something to do with our setup, or if there's something else at work!
Auto Publish Broken in 6.1.6?
Hi,
I have a problem with a site that I'm working on at the moment. It started as a 6.1.5 site, and then got updated to 6.1.6 when that was released. Now it looks like something in the database is causing the publish at functionality not to work.
If I set the value for publish at for a document, it never publishes, and nothing is logged in the error log to say that anything went wrong.
However, if I switch the database connection to a different 6.1.6 install, I can publish at with content from that database quite happily. This leads me to believe that it's something in the database rather than something in my install.
I can't figure out how the auto publishing works from looking at the source, so my question is, does anyone know what (if anything) in the DB might cause the auto publish to fail? Or can anyone point me to where I should be looking in the source for the auto publish functionality?
Auto Publish works on my 6.1.6 install, so it would indeed seem that this is not a 6.1.6 issue.
Are you able to publish manually?
Hi sir, a couple of things to check: Do you have any Umbraco events that might block the publish based upon a property value? Was the item valid for being published, i.e. any mandatory fields not complete? (basic I know but worth checking).
@Arie, I already tried a fresh 6.1.6 install and it was fine, so definitely not specific to 6.1.6. @Kieron, checked both of those, not an issue. I seem to have fixed it by rebuilding all of the Examine Indexes. I think there must have been something wrong with one of the indexes that's used by the system....... I'm going to do a bit more digging over the weekend to see if I can find out exactly what happened!
That's interesting. Why would the autopublish rely on the indexing? You'd expect the two to be independent processes or at the very least the failure of the indexing not to prevent the publishing of the content. But a corrupt index would fit the picture given that it's not failing on a default install.
Some of the v6 services and methods hit the Examine caches first, and then the database, I'm wondering if this is one of those? I haven't got too far into it, as I've fixed the immediate problem for now, but I'm going to delve into this further, as we've had a few issues on dev sites relating to the internal indexes recently, and I want to see if it's something to do with our setup, or if there's something else at work!
is working on a reply...