Search

Search results

Number of search hits: 13

Setting expire date (Dizkus)

OK I have that working and it is look like that: first operation changeExpired [code=php][/code] Operation createNewRevisionWithDate [code=php] [/code] Operation updateExpired [code=php] [/code] workflow [code=xml] Ogloszenia Everything is online immediately after creation. Zaakceptowany

Created on Feb 08, 2008

magic module (Dizkus)

immediately moderator approved createPublication Approve Approve publication for immediate publishing moderator waiting approved 1 moveOthersToDepot updatePublication Reject Reject and delete submitted content moderator waiting eraseRevision Update Update waiting publication for publishing author waiting waiting updatePublication Update+Approve Update content and approve editor approved moveToDepot createNewRevision Delete Delete publication moderator approved 0 moveToDepot deletePublication Go online Set publication online permission>moderator approved 1 Take offline Set publication offline moderator approved 0 Update+Submit Update content for approval author approved createNewRevision mailNewContentMessage Update Update content editor review updatePublication Approve Approve content for online publishing editor review approved 1 moveOthersToDepot updatePublication [/code

Created on Sep 05, 2007

Problem with user editing their own pub (Dizkus)

immediately moderator approved createPublication Approve Approve publication for immediate publishing moderator waiting approved 1 moveOthersToDepot updatePublication Reject Reject and delete submitted content moderator waiting eraseRevision Update Update waiting publication for publishing author waiting waiting updatePublication Update+Submit Update content for approval author approved createNewRevision mailNewContentMessage Update+Approve Update content and approve editor approved moveToDepot createNewRevision Delete Delete publication moderator approved 0 moveToDepot deletePublication Go online Set publication online moderator approved 1 Take offline Set publication offline moderator approved 0 Update Update content editor review updatePublication Approve Approve content for online publishing editor review approved 1 moveOthersToDepot updatePublication Reject Reject and delete submitted content moderator review eraseRevision [/code] My permissions

Created on Jan 24, 2006

MyWiki authorization problem (Dizkus)

began tracing code in Zend Studio to see where it's failing. The actual failure on updating an existing pub by it's author is on: < operation nextState="approved" online="1">createNewRevision< /operation> not on deleting the previous revision. In other words, moveToDepot works just fine, but the new revision fails. Again, my permissions are just fine; I set them up exactly as in the manual, with edit access, and the user belongs to no groups that would take any pagesetter permissions away. To prove this, I removed the createNewRevision operation in the workflow, and the error went away. So did the pub, so I changed moveToDepot to updatePublication and now everything is hunky dorry. Although I wish revision control worked. Shouldn't 'enableEditOwn' have something to do with allowing this to work? You would think so, so I did a search in all the pagesetter code for references to enableEditOwn, particular where it's value is checked, and in Zend Studio set a breakpoint at every instance. I then logged in as the user and attempted to update the pub. At no time did the code test for the value of that field. In fact, there are a few tests for it in reference to action = 'new', but that's not what we're after here. Unless I've misunderstood your meaning of "edit". Reason #2) I have pub's where I (admin) created the pub, and then entered a username into the Author field so that they could edit it. No go; can't even get to the editing form. I get an error: No workflow actions enabled - edit access not possible But I knew that if the user had created it himself he could at least get that far, so I went into the db and set the publisher id to the user's ID. That worked. So either there's a bug in which field it's looking at to verify authorship or the docs are a bit unclear as to exactly what field is being compared. Docs do say "Author" and not "publisher". I need it to work with me doing the original "create" so I can get a tid and make a link for them, so I investigated the workflow again and see: < permission>author and owner or editor< /permission> I changed it to simply "author", and it works as I need it to. Maybe it was your intention to make it require both publisher and author, or maybe the logic above is being misinterpretted. Is it: < permission>(author and owner) or editor< /permission> or < permission>author and (owner or editor)< /permission> Or what? Seems like < permission>author or owner or editor< /permission> would be more appropriate. Anyway, documented for posterity, QC or further development... Thanks

Created on Sep 14, 2005

Edit own submissions? (Dizkus)

publication for immediate publishing moderator waiting approved 1 moveOthersToDepot updatePublication Reject Reject and delete submitted content moderator waiting eraseRevision Update Update waiting publication for publishing author waiting waiting updatePublication Update+Approve Update content and approve editor approved moveToDepot createNewRevision Delete Delete publication moderator approved 0 moveToDepot deletePublication Go online Set publication online moderator approved 1 Take offline Set publication offline moderator approved 0 Update+Submit Update content for approval author approved createNewRevision mailNewContentMessage Update Update content editor review updatePublication Approve Approve content for online publishing editor review approved 1 moveOthersToDepot updatePublication

Created on Jul 04, 2005

RFC - API access - can it be overridden? (Dizkus)

Jorn, This is in regards to access checks within API calls (for example pneditapi_createPub and pneditapi_updatePub). Is it absolutely necessary to have access checks in the API? or Can this be moved to non-API function or overridden in

Created on May 20, 2005

pagesetter_editapi_updatePub attachments bug? (Dizkus)

Updating a document with doc attachment 'loses' info,setting in db fieldtype "array" value ! pagesetter_editapi_updatePub does not seems to look for 'special' fieldtypes like pagesetterFieldTypeImageUpload or pagesetterFieldTypeUpload. $Id: pneditapi.php,v 1.30 2005/01/16 18:56:22 jornlind Exp $ array php value contains: Array ( [type] => application/pdf [size] => 52083 [name] => MiniReader.pdf [url] => http://mysite.url/index.php?module=pagesetter&type=file&func=get&tid=4&pid=1&fid=doc [tmpname] => 4x1x1xdoc.dat ) Any hints? thanks

Created on Mar 22, 2005

WorkFlow Question (Dizkus)

publication for immediate publishing moderator waiting approved 1 moveOthersToDepot updatePublication updateGroup [/php] Am I missing something?

Created on Feb 18, 2005

New Workflow State? (Dizkus)

new workflow. Rejected Revision needed and then: Update Save content with no workflow change author waiting updatePublication And when updated by author, the state will then go back to "Waiting". Please share some light here on what I'm

Created on Feb 08, 2005

mywiki permission oh my! (Dizkus)

probably 90+% of what people do. So I changed the following line in mywiki.xml [code]createNewRevision[/code] to [code]updatePublication[/code] That allows the update and does not create the rev publication. The problem I am having now is that when you

Created on Jul 14, 2004

Page 1 / 2 (1 - 10 of 13 Total)

Start a new search