| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
view/theme/themename/php/theme.php instead of separate file.
|
|
|
|
| |
met. mark incompatible themes in the theme selector
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
export; this allows one to export single data sets instead of always exporting everything we know about
|
| |
|
| |
|
|
|
|
| |
'contains' (case independent substring match). Also add $request the request uri) to the supported variables.
|
| |
|
| |
|
|
|
|
| |
widget to try and get the sucker to auto submit
|
|
|
|
| |
other roles.
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
test. Update comanche doco to reflect recent changes.
|
|
|
|
| |
equals x, in_array, and array_key_exists
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
theme:schema theme selectors in settings
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
|
|