block reposting
Permalink 1 user found helpful
ok,
so anyone experience this? I have a custom block that I am working on, and it posts just fine, all is heading to the right place...ect.
however, it seems as though any time I exit edit mode and publish, and then re-edit a page to modify the block, it post to a new bID instead of updating the existing bID....but only the first time of exit/publish and re-entry for editing. after the first time it post/updates the correct line item.
it's really weird and I can't seem to find a way to guaranty posting to the correct bID.
any thoughts? I have tried an isset check and reiterate, but fail.
so anyone experience this? I have a custom block that I am working on, and it posts just fine, all is heading to the right place...ect.
however, it seems as though any time I exit edit mode and publish, and then re-edit a page to modify the block, it post to a new bID instead of updating the existing bID....but only the first time of exit/publish and re-entry for editing. after the first time it post/updates the correct line item.
it's really weird and I can't seem to find a way to guaranty posting to the correct bID.
any thoughts? I have tried an isset check and reiterate, but fail.
no one has had this in developing?
...
got something to look at? I'd take the silence as a "no" to your original question.
-frz
-frz
emailed you the block. I am pulling my hair out here. lol AKKK!
oops.
for the block I am developing I did not want versioning. I need one version of the truth so to speek.
to do this add this to your controller:
Thanks for the help Andrew!
for the block I am developing I did not want versioning. I need one version of the truth so to speek.
to do this add this to your controller:
protected $btIncludeAll = 1;
Thanks for the help Andrew!
Sorry I didn't see this thread before... I pulled my hair for the area splitter block because of this same problem. I wasn't aware you could "turn off" versioning. Ended up working around the issue in a different way... (I almost implemented my own versioning in the meantime...)
Anyway, thanks for the tip!
Anyway, thanks for the tip!
Hi Chad, I was having similar problems with the Area Splitter and decided to set btIncludeAll to 1 after reading this thread. Turned out it has some side effects!
I've filled a bug report here:
http://www.concrete5.org/community/bugs/blocks-with-btincludeall-1-...
Some additional issues may show when duplicating a page (depending how your block is coded).
Just thought I should let you know, since I got the idea originally from this thread.
I've switched btIncludeAll back to 0 in my block and I'm implementing proper versioning.
I've filled a bug report here:
http://www.concrete5.org/community/bugs/blocks-with-btincludeall-1-...
Some additional issues may show when duplicating a page (depending how your block is coded).
Just thought I should let you know, since I got the idea originally from this thread.
I've switched btIncludeAll back to 0 in my block and I'm implementing proper versioning.
lol. yup. I just had to overhaul all mine as well.
it's to bad.
hopefully core team will look into improving this capability.
it's to bad.
hopefully core team will look into improving this capability.
