aboutsummaryrefslogtreecommitdiffstats
path: root/Zotlabs/Render
Commit message (Collapse)AuthorAgeFilesLines
* don't do oembed processing on naked links and smarty lib cleanup. ported ↵Mario Vavti2019-05-132-36/+45
| | | | from zap.
* install bootstrap via composerMario Vavti2018-09-071-2/+2
|
* Fix root not added to internationalized template searchM.Dent2018-08-121-8/+11
|
* functions to support module and widget registration by plugins. These have ↵zotlabs2018-07-121-10/+24
| | | | identical construction to core modules and widgets and are registered just like hooks during addon load. Also additional Apps functions addon_app_installed() and system_app_installed() which will eventually replace feature_installed() for features which are converted to apps. The convention being used is that the module associated with the app calls the appropriate *_app_installed() function and if not present emits descriptive text about the app and exits. This allows one to click on an 'available' app and learn about it. Once installed, the app module behaves normally and may offer functionality or what once were addon settings on the settings/featured page. Refer to zap-addons in the zap repository for examples of how this is being used to eliminate the 'additional features' and 'addon settings' pages.
* remove mobile_detect (outdated and unmaintainable)zotlabs2018-02-051-27/+3
|
* install smarty via composer and update other php libsMario Vavti2017-12-181-2/+0
|
* fix loading of theme-specific widgetszotlabs2017-12-071-6/+13
|
* :bulb: Improving Doxygen documentation.Klaus Weidenbach2017-11-031-60/+119
| | | | | Fix some Doxygen parsing errors. Improve hooks documentation.
* allow plugin class widgets, fix sql error in page modulezotlabs2017-10-291-0/+3
|
* We call Theme:url() statically, make it also static.Klaus Weidenbach2017-10-231-17/+27
|
* add local_channel as a comanche condition variablezotlabs2017-10-111-0/+4
|
* typozotlabs2017-10-091-1/+1
|
* purify user-supplied filenames in some cases. Probably not needed but it's ↵zotlabs2017-10-091-0/+3
| | | | the right thing to do.
* alternate navbar layoutszotlabs2017-10-081-0/+5
|
* wiki double encoding html entitieszotlabs2017-10-041-0/+2
|
* Implemented switch statement logic in Comanche layout parser.root2017-05-081-1/+43
|
* remove include/widgets.phpzotlabs2017-03-291-2/+0
|
* use absolute namespacezotlabs2017-03-291-1/+2
|
* Comanche: allow widgets to be class based and stored appropriately in Zotlabszotlabs2017-03-291-0/+14
|
* whitespaceMario Vavti2017-02-271-2/+0
|
* do not mess up schemasMario Vavti2017-02-271-4/+6
|
* set minversion and maxversion for themes in ↵Mario Vavti2017-02-271-2/+3
| | | | view/theme/themename/php/theme.php instead of separate file.
* add a minversion to the theme and fallback to default if requirement is not ↵Mario Vavti2017-02-261-1/+6
| | | | met. mark incompatible themes in the theme selector
* fix several places where head_add_(css|js) functions have been used ↵zotlabs2017-02-191-2/+2
| | | | | | | | | | | incorrectly. It appears that mistakes were made going back a long time and propagated. Here's the way it should work: - if there is no preceding / character, we look for the file within all the appropriate theme directories. - otherwise the file should have a preceding /, which means use this path relative to the hubzilla basedir - files beginning with // are considered to be schemeless URLs. Therefore 'foo.css' means find the best theme-able representation of foo.css. '/library/foo.css' means only use the version of foo.css that is in /library.
* channel export - use a selected list of functional data categories to ↵zotlabs2017-01-311-0/+11
| | | | export; this allows one to export single data sets instead of always exporting everything we know about
* language aware contentHubzilla2017-01-201-0/+2
|
* Comanche: add greater/less than (plus greater/less than or equal) conditionalszotlabs2017-01-071-1/+31
|
* Comanche conditionals - provide a conditional "~=" form for testing ↵zotlabs2017-01-071-0/+12
| | | | 'contains' (case independent substring match). Also add $request the request uri) to the supported variables.
* comanche: simple test issueredmatrix2016-09-081-2/+1
|
* patch foundation-6.2.3 to work with jquery-3.1Mario Vavti2016-09-081-2/+2
|
* theme preview - that was easy; plus a bit more tweaking of the saved search ↵redmatrix2016-09-011-0/+2
| | | | widget to try and get the sucker to auto submit
* provide techlevels in the pro server role. Should have no visible effect on ↵redmatrix2016-08-311-0/+1
| | | | other roles.
* Before throwing a 'smarty3 dir does not exist' fatal error, try and create ↵redmatrix2016-08-281-1/+4
| | | | it. We did try and create it during install, but the template processor is initalised long before we get to that code (and throws that ugly error).
* add a couple of useful observer constructs to support identity aware pagesredmatrix2016-08-261-1/+12
|
* comanche: generalise the conditional variable usage and add $observer as a ↵redmatrix2016-08-261-19/+27
| | | | test. Update comanche doco to reflect recent changes.
* some more complex test scenarios for comanche conditionals: equals x, not ↵redmatrix2016-08-241-4/+40
| | | | equals x, in_array, and array_key_exists
* provide a mechanism for global template values (macro replacements that are ↵redmatrix2016-08-241-0/+6
| | | | available to all templates). There's a strong likelihood this list will increase but we may wish to actively prevent it from mushrooming out of control.
* don't set session theme unless logged in.redmatrix2016-08-161-0/+7
|
* move schema settings into the display settings main so we can set ↵redmatrix2016-08-151-1/+1
| | | | theme:schema theme selectors in settings
* deprecate the item_id table - replace with iconfig. A possibly useful ↵redmatrix2016-06-131-4/+5
| | | | function in the iconfig class would be a search which takes a service id and type and uid, matches against an item and returns the iid. That could save a bit of code duplication.
* move template stuff to zotlabs/renderredmatrix2016-05-204-0/+445
|
* support work for a long-term fix for issue #390, essentially one can specify ↵redmatrix2016-05-171-0/+131
| | | | 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.
* Comanche: provide a variable '$region' which can be used within a layout to ↵redmatrix2016-05-121-3/+4
| | | | make content aware of where it is on the page. For instance this can be passed as a variable to a widget and trigger either a vertical or horizontal layout depending on which region it is assigned to.
* objectify comancheredmatrix2016-05-051-0/+404