Re: Kronolith 4.1.4: Emailed iTip and Agenda's contain links that don't work properly

On Wednesday, July 30, 2014 08:25:12 AM Arne Nordmark wrote:
> 2014-07-23 22:16, Anthony Messina skrev:
> > On Wednesday, January 15, 2014 07:03:05 PM Arne Nordmark wrote:
> >> 2014-01-14 21:50, Anthony Messina skrev:
> >>> 2. Kronolith Agendas
> >>> 
> >>> When I enable the Kronolith agenda's via cron, I have noticed that the
> >>> URLs for the events do not include the Horde prefix and show events such
> >>> as the following.  Horde alarm emails do not have this issue, nor do
> >>> iTip emails.
> >>> 
> >>> https://example.com/kronolith/event.php?eventID=... <snipped>
> >>> 
> >>> instead of
> >>> 
> >>> https://example.com/horde/kronolith/event.php?eventID=... <snipped>
> >> 
> >> I remember having this problem, and I remember creating a file
> >> registry.local.php with the content:
> >> <?php
> >> $app_webroot = '/horde';
> >> 
> >> I am not 100% certain that these two were connected, but you may try it.
> >> I also had to set environment variable HTTPS=on to force https:// in the
> >> agenda mails.
> >> 
> >> Arne
> > 
> > I wanted to wait until the upgrade to Horde 5.2 to see if this would have
> > been fixed by some other method, which it wasn't.  I have worked around
> > this issue by using your suggestion above.  It is still strange to me
> > that none of the other apps require this manual addition in
> > registry.local.php:
> > 
> > $app_webroot = '/horde';
> 
> I guess in almost all cases, mails are sent out as a (perhaps indirect) 
> result of some web action, and the apps have access to the full URI that 
> was used. Thus this problem would only show up when mails are sent due 
> to a cron job or similar where the is no URI available.
> 
> Alarm emails sent out through a cron job during periods of no web 
> activity could show this problem I guess. Are you thinking of any other 
> cases?

The reason why I brought it up in the first place is that horde-alarm does not 
require setting $app_webroot to get the URL set properly, whereas kronolith-
agenda does, at least in my case.  They are both initiated in the same cron-
like manner, though I am using systemd timers.

It was the fact that they exhibited different behavior that led me to bring it 
up as an issue.

-A

-- 
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlPYkgMACgkQktw13LABSk4BVgCfa1pADJsSzN+lNtDxtCpLTYhe
vyEAnjpYIOCXOtTeOgMhGnK0YF9ZoHBs
=KIvy
-----END PGP SIGNATURE-----