Re: Event notification from another user private calendar
Jens Wahnes <[email protected]> Fri, 19 Feb 2016 00:47:45 +0100
| Newsgroups | gmane.comp.horde.kronolith |
|---|---|
| Organization | Wahnes World |
| Message-ID | <[email protected]> |
On Thu, Feb 18 2016, at 17:18:34 -0500, Michael J Rubinsky wrote: > Quoting Luis Felipe Marzagao <[email protected]>: >> Em 18/02/2016 18:31, Michael J Rubinsky escreveu: >>> Quoting Jens Wahnes <[email protected]>: >>>> SELECT * FROM kronolith_sharesng WHERE share_name = 0 [pid 18524 on >>>> line 321 of "/usr/share/pear/Horde/Db/Adapter/Mysqli.php"] >>> This is probably coming from Kronolith_Application::listAlarms(). >>> >>> As an admin user, execute the following from the admin phpshell page, >>> using kronolith's scope: >>> You should see an array of share_names. If I'm right, one of these will >>> be '0' for some unknown reason. >> >> Yep, for me it does. The 23th item: >> [23]=> >> int(0) Similar thing here, only that it was the first (index 0) element of the array. > This means that the share in the database doesn't have a share_name for > some reason. Can you see which share that is in the kronolith_sharesng > table? Yes, there was an entry that - beside the share_id - was completely "empty", that is share_name was empty, share_owner was NULL and all permissions were 0. I deleted that empty share entry in kronolith_sharesng, removed all duplicated entries from horde_alarms and reran the horde-alarms script. No duplicate entries were re-created. Yippee. Now for how that empty kronolith_share was created, I don't really know. If I go by the share_id, it must have been created back in the time when we ran Horde 3 (or Horde 2 even). But maybe it wasn't created that way but got changed to that later on? Hopefully Luis can shed some light on that from his case - he seems to have far less users/shares than we do. Jens -- kronolith mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAlbGWCAACgkQAL/arBo1HgjzkwCgxcVKjQJWoVdkpeRO3Yv5LiBX cN4An1hAOyNmXG4+UIvR5C5VQB1dCvUc =o8h+ -----END PGP SIGNATURE-----