volse-hubzilla.git - Volse Hubzilla -- soft fork of main Hubzilla core for Volse

	Commit message (Collapse)	Author	Age	Files	Lines
*	We call Theme:url() statically, make it also static.	Klaus Weidenbach	2017-10-23	1	-17/+27
\|
*	whitespace	Mario Vavti	2017-02-27	1	-2/+0
\|
*	do not mess up schemas	Mario Vavti	2017-02-27	1	-4/+6
\|
*	set minversion and maxversion for themes in ↵	Mario Vavti	2017-02-27	1	-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 Vavti	2017-02-26	1	-1/+6
\| \| \| \|	met. mark incompatible themes in the theme selector
*	fix several places where head_add_(css\|js) functions have been used ↵	zotlabs	2017-02-19	1	-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.
*	theme preview - that was easy; plus a bit more tweaking of the saved search ↵	redmatrix	2016-09-01	1	-0/+2
\| \| \| \|	widget to try and get the sucker to auto submit
*	don't set session theme unless logged in.	redmatrix	2016-08-16	1	-0/+7
\|
*	move schema settings into the display settings main so we can set ↵	redmatrix	2016-08-15	1	-1/+1
\| \| \| \|	theme:schema theme selectors in settings
*	support work for a long-term fix for issue #390, essentially one can specify ↵	redmatrix	2016-05-17	1	-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.