aboutsummaryrefslogtreecommitdiffstats
path: root/mod/events.php
Commit message (Collapse)AuthorAgeFilesLines
* lost ability to delete eventsfriendica2015-02-151-0/+31
|
* bring some styling back to the colorbox and improve the event preview abilityfriendica2015-02-091-0/+12
|
* event form - provide map ability for location field and add preview abilityfriendica2015-02-091-0/+9
|
* help text for the "adjust for viewer timezone" toggle switch since you ↵friendica2015-02-081-1/+1
| | | | apparently need an IQ of 230 or greater to be able to use it correctly.
* make default calendar view ambivalent to the state of the ignore flag.friendica2015-02-081-3/+2
|
* style the checkboxes in the event formfriendica2015-02-051-1/+1
|
* event form cleanup backported from trinidad - still need to style the checkboxesfriendica2015-02-051-3/+4
|
* local_user => local_channelfriendica2015-01-281-16/+16
|
* Allow tags in event description and locationStefan Parviainen2015-01-131-0/+4
|
* add event export (this month) to event UIfriendica2014-11-241-0/+12
|
* Switch to a better datetime picker widgetStefan Parviainen2014-11-161-5/+4
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* If entered event info is not valid, let user try again with the old info ↵Stefan Parviainen2014-10-211-7/+26
| | | | still there. Closes friendica/red#648
* Don't display date format, it's already in the placeholder textStefan Parviainen2014-10-191-6/+0
|
* Changes in the datetimesel api, prevent user from picking event end date ↵Stefan Parviainen2014-10-191-2/+2
| | | | earlier than start date
* Give an error if event is supposed to end before it starts. Closes ↵Stefan Parviainen2014-10-191-2/+4
| | | | friendica/red#534
* Initial stab at better general datetime pickerStefan Parviainen2014-10-181-17/+2
|
* missing event permissionsfriendica2014-10-151-0/+1
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* add categories to eventsfriendica2014-09-071-1/+50
|
* more work on the event edit formfriendica2014-09-051-0/+2
|
* put a date and time picker on eventsfriendica2014-09-041-5/+29
|
* numerous event fixes - mostly related to editing an eventfriendica2014-07-061-22/+41
|
* rule of snakes #1, kill the snake.friendica2014-06-281-2/+2
| | | | | | tinymce is gone. if you want a visual editor, figure out what you want and make it happen. If you don't want a visual editor, do nothing. This is in the community's hands. I don't need a visual editor.
* only show jotnets when posting conversation itemsfriendica2014-06-141-1/+1
|
* use consistent capitalisation in the item actions menufriendica2014-05-291-1/+1
|
* newevent: front end functionsfriendica2014-05-291-3/+13
|
* start to tie in the new event logicfriendica2014-05-291-2/+3
|
* event form hard-wired tinymce=on, made selectablefriendica2014-05-081-2/+11
|
* issue #395, item 2friendica2014-04-061-1/+4
|
* dav: throw exception if channel for requested DAV directory is deletedfriendica2014-01-151-2/+1
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-1/+1
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* need include/conversation for events nowfriendica2013-12-061-0/+1
|
* some work on events permissionsfriendica2013-12-011-6/+17
|
* make "selected" class work on all navigation menu itemsmarijus2013-08-011-0/+2
|
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-2/+2
| | | | 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.
* some fixes related to eventsMichael Johnston2013-03-071-4/+5
| | | | | | | - 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
* progress on tag deliveryfriendica2013-02-111-1/+1
|
* documenting event-finish-date-crosses-month-boundary issue to come back to laterfriendica2013-01-161-0/+6
|
* mopping up the events issues so I can move on to other stufffriendica2013-01-161-2/+4
|
* still some bugs but events are happening again.friendica2013-01-151-42/+35
|
* events are still buggered and aren't anywhere close to working, but not ↵friendica2013-01-071-8/+9
| | | | buggered quite as much as before.
* fix show-stopping bugsZach Prezkuta2013-01-061-2/+2
|
* wall posts now display - address book structure revamp startedfriendica2012-10-101-0/+1
|
* separate the public feed from everything elsefriendica2012-09-201-1/+17
|
* convert ent_quotes for jquery calendar title/summaryfriendica2012-06-291-2/+2
|
* create third privacy state - public post but not searchable or publicly visiblefriendica2012-06-281-1/+1
|
* change event behaviour so that title is required but description is notfriendica2012-06-251-6/+6
|
* event summary/titlefriendica2012-06-251-3/+11
|
* events: fix select events queryfabrixxm2012-06-071-2/+2
| | | | | select events that starts before display start date and/or ends after display end date.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 11:42:34 +0000