Summary | No frameset after maintenance |
Queue | Horde Base |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | jan (at) horde (dot) org |
Created | 12/18/2004 (7585 days ago) |
Due | |
Updated | 01/15/2005 (7557 days ago) |
Assigned | 12/19/2004 (7584 days ago) |
Resolved | 01/15/2005 (7557 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
New Attachment: maintenance2.diff
have it archived. Maybe it might be of some use some time in the future.
big item I wrote for Horde before I was a developer. I'm not sure how
I got CVS access after this (maybe it was because no one else
understands the code :) ) But it has been in the codebase for 2-3
years so ripping it out before the next release doesn't seem to make
sense, to me at least.
complicated. But I gave up rewriting this without retarding the
release even more.
I get the frameset after logging in, not before, and I get the
maintenance directly after logging in. Loading the frameset is fixed
now, as well as being able to login at all.
I still get redirected to IMP instead of the preferred application
after running maintenances, and the maintenance tasks are skipped if I
simply reload the confirm page, rendering the agree maintenance type
useless. But these are no showstoppers for the release anymore.
New Attachment: imp.png
New Attachment: maintenance_2.png
New Attachment: maintenance_1.png
run 2 - a TOS agreement and purge trash). This is task screen 1.
New Attachment: login_screen.png
and I don't believe there is any reason to rewrite the code. Attached
you will find screenshots of a session where maintenance tasks get
performed.
New Attachment: maintenance.diff
shouldn't get shipped with Horde 3.0. I have no idea if we will be
able to fix this in time, but here is what I got for today, maybe
someone understands where I'm heading and can complete this. Otherwise
I'll try to finish this tomorrow.
all. I'm really having a hard time to trace this code, but I'll keep
trying to fix this.
any of the code that would cause the undefined errors - it seems to be
working for my test cases.
twice before the page gets redirected back to imp/login.php:
Notice: Undefined variable: sessArray in
/home/jan/headhorde/imp/redirect.php on line 137
Using application/imp auth.
Assigned to Michael Slusarz
State ⇒ Assigned
where URLs are generated.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ No frameset after maintenance
Queue ⇒ Horde Base
State ⇒ Unconfirmed
and the initial_application pref isn't honoured either.