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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Work around possible loop and use Lib/Config in init	Mario Vavti	2024-01-01	1	-2/+0
\|
*	move App::$install check to Config::Load() as suggested by Harald	Mario	2023-12-20	1	-7/+2
\|
*	Merge branch 'fix-config-deserialization' into 'dev'	Mario	2023-12-20	1	-6/+15
\|\ \| \| \| \| \| \| \| \|	Fix deserialization of config values broken by 69266cd6. See merge request hubzilla/core!2077
\| *	Fix deserialization of config values broken by 69266cd6.	Harald Eilertsen	2023-12-17	1	-6/+15
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This should fix issue #1828. This patch makes it explicit that we store arrays in the config as json encoded arrays, while we allow both json encoded and PHP serialized arrays to be deserialized correctly. Unless it's a brand new install, the existing data in the database will be PHP serialized. I've also added a hardening measure in case we fall back to PHP unserialize, making sure we're not vulnerable to a PHP Object Injection attack. This means that deserializing arrays containing PHP objects will no longer work, but afaict we never do that anyways, so I don't think that should break anything.
* \|	fix loop as described in issue #1827	Mario	2023-12-17	1	-0/+6
\|/
*	check return from Config::Load() and retry on failure plus cleanup	Mario Vavti	2023-12-14	1	-30/+57
\|
*	mod_search: fix the group by mess	zotlabs	2018-01-21	1	-2/+2
\|
*	:bulb: Improving Doxygen documentation.	Klaus Weidenbach	2017-11-03	1	-15/+14
\| \| \| \| \|	Fix some Doxygen parsing errors. Improve hooks documentation.
*	grrr. stop making branding assumptions.	zotlabs	2017-03-12	1	-1/+1
\|
*	minor changes to config api and markdown_to_bb	zotlabs	2016-12-05	1	-3/+3
\|
*	begin moving config to zotlabs. Leave procedural stubs for backward ↵	redmatrix	2016-05-30	1	-0/+166
	comaptibility