I've noticed that the content created within the AutoFolder folders is being published on create - Is this a known issue, and is there a way to stop it?
I've confirmed it isn't happen to non-AutoFolder folders, and reproduced it several times.
K - so it looks like there are event handlers registered for both New + Publish:
public ApplicationBase()
{
Document.New += new Document.NewEventHandler(Document_New);
Document.AfterPublish += new Document.PublishEventHandler(Document_New);
}
I've had a quick go at getting it to Save on a New document, though I', getting problems with it creating duplicate letter folders (e.g. 'M (1)'). Will report back - any feedback welcome in the meantime...
I might see if I can get Tim to update the official release on the Umbraco AutoFolders project page to include this patch. (he's down as a project contributor)
So, if the version from CodePlex builds fine, but after you apply the patch it doesn't, I'd suggest downloading the two .patch files (mine and ProNotions) - and rathern than applying the patch you can simply open it up with TortoiseSVN (opens with TortoiseUDiff viewer automatically I believe) - you'll then be able to see which lines have changed and change them manually in your source.
Hopefully, one day we'll get access to CodePlex to accept the patch commits, but Chris is a bit busy I think.
(the only other option is to create a new CodePlex entry for it....but I'm not so sure about it, since its Chris' project)
Thanks for that - I was thinking about doing that exact thing this morning - I am getting my head around Tortoise / SVN so will be working through your suggestion over the next few days.
Is the auto-publishing problem meant to be fixed in version 2.03 or do you need to patch the source to fix it? I'm currently using 2.03 and it auto publishes every node it creates.
I'm not to keen on going back to SVN and causing problems with my Hg and git setup, If someone has an updated dll how about sharing a link?
AutoFolders auto-publishing?
I've noticed that the content created within the AutoFolder folders is being published on create - Is this a known issue, and is there a way to stop it?
I've confirmed it isn't happen to non-AutoFolder folders, and reproduced it several times.
*Bump* - Can anyone help on this one? I'm using Umbraco 4.5.2
K - so it looks like there are event handlers registered for both New + Publish:
Then regardless, it's calling:
I've had a quick go at getting it to Save on a New document, though I', getting problems with it creating duplicate letter folders (e.g. 'M (1)'). Will report back - any feedback welcome in the meantime...
Hi,
I'm having the same issue. Did you find a solution or workaround for this?
Thanks,
Chris
Has anyone patched the source to stop it auto publishing?
Regards
Ismail
Finally submitted as a patch to codeplex: http://autofolders.codeplex.com/SourceControl/list/patches
Autopublish now works, plus some other bug fixes and extra providers.
Hey Drew
'xcuse my ignorance but how do you apply the patch ?
I downloaded the file from codeplex - it is a .patch file but not sure on "where to from here"...
Cheers
Nigel
If you check-out or download the source from Codeplex, its managed by SVN - you can then apply the .patch file.
This might help:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-patch.html
I might see if I can get Tim to update the official release on the Umbraco AutoFolders project page to include this patch.
(he's down as a project contributor)
Cheers,
Hi Drew
Finally getting back to this...
I have downloaded the source for the project, ran a test build, and the project built OK.
I then downloaded the patch and applied it via Tortoise SVN, but when doing a rebuild I now get the following error:
umbraco.BasePages.BasePage' does not contain a definition for 'Current'
E:\SVN Source Code\Umbraco Autofolders\AutoFolder\ApplicationBase.cs
So just wondering if you are able to provide any ideas/suggestions - I am a bit stumped.
My site is 4.5.2 and running ASP.NET3.5, just in case this helps.
Cheers
Nigel
Sorry Nigel, been out of the loop for a bit!
So, if the version from CodePlex builds fine, but after you apply the patch it doesn't, I'd suggest downloading the two .patch files (mine and ProNotions) - and rathern than applying the patch you can simply open it up with TortoiseSVN (opens with TortoiseUDiff viewer automatically I believe) - you'll then be able to see which lines have changed and change them manually in your source.
Hopefully, one day we'll get access to CodePlex to accept the patch commits, but Chris is a bit busy I think.
(the only other option is to create a new CodePlex entry for it....but I'm not so sure about it, since its Chris' project)
Cheers,
Drew
Hi Drew
Thanks for that - I was thinking about doing that exact thing this morning - I am getting my head around Tortoise / SVN so will be working through your suggestion over the next few days.
Thanks for your help / feedback
Cheers
Nigel
Is the auto-publishing problem meant to be fixed in version 2.03 or do you need to patch the source to fix it? I'm currently using 2.03 and it auto publishes every node it creates.
I'm not to keen on going back to SVN and causing problems with my Hg and git setup, If someone has an updated dll how about sharing a link?
Cheers
Evan
Hi
This worked for me
is working on a reply...