aboutsummaryrefslogtreecommitdiffstats
path: root/include/plugin.php
Commit message (Collapse)AuthorAgeFilesLines
* optional server role compatibility checks for pluginsredmatrix2016-08-221-0/+12
|
* issue #411redmatrix2016-07-191-0/+1
|
* fix absolute .js urlsTreer2016-06-261-1/+1
|
* Allow absolute links to css and js filesTreer2016-06-251-8/+20
|
* code optimisationredmatrix2016-06-201-0/+6
|
* remove debuggingredmatrix2016-06-111-1/+0
|
* Work supporting issue #411, add an optional priority (int) as a second arg ↵redmatrix2016-06-111-11/+23
| | | | | | to head_add_js to affect the load ordering, larger numbered priorities will be included after lower numbered ones. Default priority is 0.Note that we treat main.js differently and always add main.js to the page last, regardless of any other ordering.
* provide a sort of mutex lock around db logging so it can't possibly recurse. ↵redmatrix2016-05-311-9/+12
| | | | Previous attempts to do something similar using other methods haven't worked out satisfactorily.
* don't remove missing hooks while update_r1169 is happpening - temp fixredmatrix2016-05-311-5/+8
|
* start removing reserved words from database column names (this run: addon ↵redmatrix2016-05-301-11/+11
| | | | and hook)
* code cleanupredmatrix2016-05-241-6/+5
|
* move template stuff to zotlabs/renderredmatrix2016-05-201-2/+0
|
* support work for a long-term fix for issue #390, essentially one can specify ↵redmatrix2016-05-171-2/+3
| | | | a theme:schema string anywhere a theme is input. It will be honoured unless an existing schema setting over-rides this behaviour. This should also be backward compatible but the theme selection code has been cleaned up slightly and there may be subtle differences in behaviour after this commit. On my site this required a page refresh as the first page load after this change was a bit confused.
* this should work to call a hook for a string class methodredmatrix2016-04-231-2/+12
|
* Class method support for hooksredmatrix2016-04-231-2/+3
|
* Merge branch 'dev' of https://github.com/redmatrix/hubzilla into dev_mergeredmatrix2016-04-211-5/+11
|\
| * add querystring to css and js which is added via head_add_{css, js}Mario Vavti2016-04-191-5/+11
| |
* | new hook interface (the old one still works but requires handlers to have ↵redmatrix2016-04-211-13/+13
|/ | | | two calling arguments; the first of which is no longer used). The new interface is called from Zotlabs\Extend\Hook::register() and allows you to specify which hook version to use. The default will be the new interface with one function argument. We also implement the hook priority field which was always there but needed to be set manually in the DB. This provides a way for two hook handlers that implement the same hook interface to determine which order to be called in the event of conflicts.
* static Appredmatrix2016-03-311-27/+27
|
* deprecate $a->get_baseurl()redmatrix2016-03-301-2/+2
|
* add 'requires' field to plugin info to list other dependent plugins/addons ↵redmatrix2016-02-241-1/+18
| | | | and disable if dependencies are not installed/enabled
* Provide Zotlabs\Project and System class for querying details about the ↵redmatrix2016-02-181-11/+0
| | | | project/version info. Move these out of /boot.php
* whitespaceredmatrix2016-02-111-1/+1
|
* minversion issueredmatrix2016-01-171-2/+2
|
* logic reversal in version checkingredmatrix2016-01-111-3/+3
|
* plugin version compatibility checking. To use, set MinVersion, MaxVersion or ↵redmatrix2016-01-111-5/+32
| | | | MinPHPversion in the plugin header block. Case is not important. We check the project versions against STD_VERSION, which should be rolled to a new y of x.x.y if the plugin interface or project code changes in an incompatible way.
* start on refactor of plugin/theme/widget info block parsingredmatrix2015-12-221-8/+8
|
* use realpath to bypass symlinks and check actually directoryredmatrix2015-12-181-0/+10
|
* use the channel blacklist for items and mail, still todo: directory and stuffredmatrix2015-12-031-0/+9
|
* introduce STD_VERSION and get_std_version() [in include/plugin.php], we ↵redmatrix2015-12-021-0/+11
| | | | begin with 0.11.1 since it is an incompatible interface change to 0.11.
* make use of http_host vs. server_name configurable in script_path()redmatrix2015-10-251-2/+10
|
* Better handling for SSL reverse proxyStefan Krauth2015-10-251-7/+2
|
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-21/+23
| | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
* Fix SQL query for removing orphan hooks.Klaus Weidenbach2015-03-101-31/+58
| | | | | initialize some variables before using them. commented out some unused variables.
* detect https coming through reverse proxy or load balancer using ↵friendica2015-01-051-0/+2
| | | | x-forwarded-proto instead of (actually in addition to testing) $_SERVER['HTTPS'] and/or $_SERVER['SERVER_PORT'] to indicate ssl is enabled
* 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)
* allow site specific templates, css, js, whateverfriendica2014-09-301-0/+1
|
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-031-87/+0
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* rename friendica_smartyfriendica2014-07-131-1/+3
|
* Documented include/plugin.php a bit and removed an annoying defaultKlaus Weidenbach2014-07-011-107/+114
| | | | logging. Changed it to LOGGER_DEBUG.
* load main.js lastfriendica2014-06-131-1/+15
|
* some backend stuff for appsfriendica2014-05-151-0/+11
|
* always load css and js sources using the same url as the page that is being ↵friendica2013-12-121-2/+24
| | | | visited so there is no http/https mismatch.
* head_remove_css, head_remove_jsfriendica2013-12-111-1/+17
|
* remove hook logging - too noisyfriendica2013-12-011-1/+1
|
* hooks getting called twicefriendica2013-11-301-1/+3
|
* allow themes to mess with the navbar contents without a custom template. ↵friendica2013-11-281-2/+35
| | | | | | | | | | | | It's done as a callback using a transient plugin hook. For instance to get rid of the notifications link: insert_hook('nav','strip_notify'); function strip_notify($a,&$b) { unset($b['nav']['notifications']); }
* fix plugin and them toggles for the colourblind, add theme info block and ↵friendica2013-11-181-2/+2
| | | | recent screenshot to redbasic
* Service classChristian Vogeley2013-09-081-7/+12
| | | | identity, follow, photo upload, att upload
* fix intltext template driverfriendica2013-05-151-1/+1
|