aboutsummaryrefslogtreecommitdiffstats
path: root/include/event.php
Commit message (Collapse)AuthorAgeFilesLines
* event parse cleanupredmatrix2015-07-301-2/+8
|
* escape $ in eventsredmatrix2015-07-301-2/+8
|
* minor cleanupredmatrix2015-07-291-14/+1
|
* Merge branch 'vobject'redmatrix2015-07-291-23/+83
|\ | | | | | | | | Conflicts: include/event.php
| * convert ics import to sabre/vobjectredmatrix2015-07-291-29/+42
| |
| * initial work on using sabre as a vcalendar parserredmatrix2015-07-281-1/+50
| |
* | PRIVACY: imported eventsredmatrix2015-07-291-0/+1
|/
* make superblock block a channel if it's an owner as well as the current ↵redmatrix2015-07-281-1/+1
| | | | author; add @hostname to event hashes to make their use in vcalendar more RFC compliant
* crude but more or less functional event import from thunderbird ics filesredmatrix2015-07-261-6/+25
|
* backend code for importing events from "simple" ics calendar files.redmatrix2015-07-261-0/+65
|
* ics calendar export - commas need to be escapedredmatrix2015-07-211-1/+1
|
* product was a bad string to use because we may require it for e-commerce, ↵redmatrix2015-05-131-1/+1
| | | | and RED_PLATFORM is equally problematic for other reasons.
* force event obj_type on updatefriendica2015-04-201-1/+2
|
* Fixed two wrong variable usages in event.php.Klaus Weidenbach2015-03-291-58/+65
| | | | I just checked the code, not the functionality.
* ical output wasn't using 24-hour timefriendica2014-11-241-2/+2
|
* basic vcalendar formatting supportfriendica2014-11-231-0/+50
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* wrong permalink on remote eventsfriendica2014-10-231-4/+10
|
* add categories to eventsfriendica2014-09-071-0/+24
|
* numerous event fixes - mostly related to editing an eventfriendica2014-07-061-1/+1
|
* make system generated birthday events un-commentable since comments won't go ↵friendica2014-06-031-2/+17
| | | | where you think.
* bring back birthdaysfriendica2014-06-021-3/+5
|
* issue #477friendica2014-06-011-2/+2
|
* testing new event codefriendica2014-05-291-6/+12
|
* more work on new event codefriendica2014-05-291-58/+46
|
* event_addtocal function for storing received eventsfriendica2014-05-291-6/+52
|
* start to tie in the new event logicfriendica2014-05-291-1/+1
|
* split event storage into two bits - separate the event storage from the ↵friendica2014-05-291-65/+77
| | | | associated item storage
* better event managementfriendica2014-05-071-15/+40
|
* version updatefriendica2014-03-111-1/+1
|
* some minor cleanup on plinks for some very subtle permissions issuesfriendica2014-01-091-0/+2
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-10/+10
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-1/+2
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* Merge https://github.com/friendica/red into zpullfriendica2013-03-211-1/+3
|\
| * small fixes for eventsMichael Johnston2013-03-211-1/+3
| |
* | rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-4/+4
|/ | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
* cleanupfriendica2013-03-101-68/+0
|
* some fixes related to eventsMichael Johnston2013-03-071-1/+1
| | | | | | | - add backticks around column "desc" in sql query - fixed query for data passed to showEvent - showEvent was picking up on id from item instead of id from event - fixed references to author info in template
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* preserve event item[uri] if presentfriendica2013-01-201-27/+35
|
* more heavy lifting on API - though need to re-visit events and give them all ↵friendica2013-01-191-4/+4
| | | | message_ids from the origination site.
* mopping up the events issues so I can move on to other stufffriendica2013-01-161-10/+9
|
* import events (not just event posts) from zotfriendica2013-01-161-4/+1
|
* still some bugs but events are happening again.friendica2013-01-151-5/+5
|
* events backend heavy lifting - the new structure is slowly emerging.friendica2013-01-151-77/+87
|
* slow progress on events, one step forward, one step back.friendica2013-01-151-14/+26
|
* events are still buggered and aren't anywhere close to working, but not ↵friendica2013-01-071-4/+6
| | | | buggered quite as much as before.
* wall posts now display - address book structure revamp startedfriendica2012-10-101-9/+11
|
* Can't see any posts currently - after the big shakeup, but we can now post ↵friendica2012-10-031-1/+1
| | | | top level activities and store them.
* item table rename parent-uri, target-type, object-type (more to come later)friendica2012-08-151-2/+2
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 07:43:21 +0000