Hi Tim! Sorry about not replying earlier, but I have not been following the list so closely these days, and to be honest an immediate solution didn't come to mind. I was hoping Patrick would come up with some kind of trick to get the login page to come up... But either he doesn't have a solution, or he's not following this thread.
Glad you found a solution, but like you, I don't think having duplicate pages is ideal. Even if you use an include directive to prefill one page content with the other. (I hope you are doing that). Now, if I understand you correctly, you want a login page to popup when a person is not authorized to submit a zap form... Thinking about it more, there may be a simple way to do this. How about something like this: Not tested... (:if ! auth zap:) Show an update button that goes to a login page. That login page then proceeds to the update form. (:if auth zap && equal {$myaction} "Update" :) Show the update form (:if auth zap && ! equal {myaction} "Update":) Just show the update button (:if:) This should give you roughly what you want. Let me know if you have any questions about the specifics of the implementation, but it looks like you're coming along great in the basic ZAP code, so I'm confident you can take it from here... Cheers, Dan _______________________________________________ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users