Tickets :: [#11648] nag bug on save or edit a task

6.0.0-alpha12

6/7/25

Summary	nag bug on save or edit a task
Queue	Nag
Queue Version	4.0.0
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	strimpak.geo (at) gmail (dot) com
Created	11/06/2012 (4596 days ago)
Due
Updated	02/23/2013 (4487 days ago)
Assigned
Resolved	11/06/2012 (4596 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

02/23/2013 11:56:55 PM	mussi (at) snoop (dot) alphanet (dot) ch	Comment #8	Reply to this comment
Basically, the trick is to check the complete apache installation. In my case, the virtual directory for horde was fine, but the root directory contained a "AllowOverride None" clause which broke things.

11/15/2012 08:41:20 PM	trefz (at) gmx (dot) net	Comment #7	Reply to this comment
Which is not working. I just thought it's maybe related to this issue, somehow.

11/15/2012 08:27:48 PM	Michael Rubinsky	Comment #6	Reply to this comment
You should, because the rewrite fix will alow to create/edit/delete/tasks in the web interface but still prevents tasks being "create" by a syncml sync with a remote device; while syncing of web interface created tasks still works What does this have to do with SyncML? That uses a completely different mechanism for "saving" tasks.

11/15/2012 08:09:32 PM	trefz (at) gmx (dot) net	Comment #5	Reply to this comment
You should, because the rewrite fix will alow to create/edit/delete/tasks in the web interface but still prevents tasks being "create" by a syncml sync with a remote device; while syncing of web interface created tasks still works

11/15/2012 08:01:18 PM	Michael Rubinsky	Comment #4	Reply to this comment
got the same problem using nag with lighttpd; solved it with this rewrite rule for lighttpd:http://code.ohloh.net/file?fid=cpQi1iXW5kxJXlfaZnip9hxP6Vk&cid=WimrOJAKYSo&s=&browser=Default#L0 This is already included in the lighttpd rules in nag. See nag/docs/lighttpd.conf funny thing: i had pretty urls disabled but nag stil used it. Maybe thats worth a bug ticket?! Yes, this was a design flaw that made it into production. The pretty urls are for user-visible urls. The only urls affected are the save/delete urls that the user does not see. We are probably going to remove the use of these controllers in the next release.

11/15/2012 07:49:55 PM	trefz (at) gmx (dot) net	Comment #3	Reply to this comment
got the same problem using nag with lighttpd; solved it with this rewrite rule for lighttpd:http://code.ohloh.net/file?fid=cpQi1iXW5kxJXlfaZnip9hxP6Vk&cid=WimrOJAKYSo&s=&browser=Default#L0 funny thing: i had pretty urls disabled but nag stil used it. Maybe thats worth a bug ticket?!

11/06/2012 10:21:08 AM	Jan Schneider	Comment #2 Priority ⇒ 1. Low State ⇒ Not A Bug	Reply to this comment
Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists.

11/06/2012 09:38:51 AM	strimpak (dot) geo (at) gmail (dot) com	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ nag bug on save or edit a task Queue ⇒ Nag Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
I have installed groupware webmail edition (H5) with nag (4.0.0) Final. I found a bug in my installation when I was going to add a new task or edit a task allready exists. I checked that there is the same bug at: http://demo.horde.org when adding or editting a task it tries to write a url: http://demo.horde.org/nag/t/save and it sends a 404 error The requested URL /nag/t/save was not found on this server. I took a glance to the code and I think that nag is an mvc application that either router or controller does not work well. please take a look at this and provide a solution.