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

	Commit message (Collapse)	Author	Age	Files	Lines
*	release the navbar in landscape mode on small devices	marijus	2014-11-05	1	-0/+7
\|
*	changed notification description	friendica	2014-11-04	1	-1/+1
\|
*	minor adjustments to make the form work as designed	friendica	2014-11-04	2	-8/+12
\|
*	ok heads up - potentially destabilising change. I've tried to sort out all ↵	friendica	2014-11-04	10	-42/+81
\| \| \| \| \| \| \| \| \| \|	the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
*	Merge https://github.com/friendica/red into pending_merge	friendica	2014-11-04	1	-11/+0
\|\
\| *	Remove legacy custom/	Thomas Willingham	2014-11-04	1	-11/+0
\| \|
* \|	configurable visual alerts/notifications	friendica	2014-11-04	5	-73/+206
\|/
*	it appears bootbox was lost in a bootstrap upgrade	friendica	2014-11-04	3	-1/+901
\|
*	class > id mixup	marijus	2014-11-04	1	-1/+1
\|
*	missing </div>	marijus	2014-11-04	1	-2/+3
\|
*	wall posted comment to a top-level wall post which arrived via a route (e.g. ↵	friendica	2014-11-03	1	-0/+3
\| \| \| \|	was posted to a forum) had no route, hence downstream recipients report route mismatch
*	posted-date-selector - spacing was slightly off in dropdown entries	friendica	2014-11-03	1	-0/+4
\|
*	Merge https://github.com/friendica/red into pending_merge	friendica	2014-11-03	5	-91/+99
\|\
\| *	innodb issue	Thomas Willingham	2014-11-03	1	-2/+3
\| \|
\| *	one </div> to much and css fixes	marijus	2014-11-03	2	-79/+79
\| \|
\| *	Merge branch 'master' of https://github.com/friendica/red	marijus	2014-11-03	3	-1/+377
\| \|\
\| * \|	if uploading a photo go away to album	marijus	2014-11-03	1	-2/+7
\| \| \|
\| * \|	if deleting a photo go away to album	marijus	2014-11-03	2	-8/+10
\| \| \|
* \| \|	various UI issues related to having an enormous number of entries in the ↵	friendica	2014-11-03	3	-5/+47
\| \|/ \|/\| \| \| \| \|	posted_date selector including years/months that had no posts
* \|	provide example import script	friendica	2014-11-03	3	-1/+377
\|/
*	php warnings	friendica	2014-11-02	1	-23/+23
\|
*	Merge https://github.com/friendica/red into pending_merge	friendica	2014-11-02	6	-24/+23
\|\
\| *	Pixelbit restored. Going forwards, we probably want to add a check	Thomas Willingham	2014-11-02	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \|	that a directory is returning something in find_upstream_directory() since this was spotted by a new install who thought they were broken.
\| *	Merge branch 'master' of https://github.com/friendica/red	marijus	2014-11-02	1	-1/+0
\| \|\
\| \| *	Remove pixelbits from directory fallback - blocked public searches provide	Thomas Willingham	2014-11-02	1	-1/+0
\| \| \| \| \| \| \| \| \| \| \| \|	no results.
\| * \|	css fixes	marijus	2014-11-02	5	-23/+22
\| \|/
* /	I'm going to try again with the conversation request packets. I've looked ↵	friendica	2014-11-02	2	-13/+60
\|/ \| \| \|	this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't think this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
*	add some more safety checks before turning the conversation request messages ↵	friendica	2014-11-02	3	-5/+7
\| \| \| \|	back on
*	even more photos work	marijus	2014-11-01	6	-160/+103
\|
*	close the eventual open tool if the other opens	marijus	2014-11-01	1	-2/+2
\|
*	check that we have valid data	friendica	2014-11-01	2	-10/+17
\|
*	Merge https://github.com/friendica/red into pending_merge	friendica	2014-11-01	12	-87/+70
\|\
\| *	do not reload page for photo upload	marijus	2014-10-31	9	-43/+26
\| \|
\| *	Smarty3 now lives in store	Thomas Willingham	2014-10-31	1	-4/+0
\| \|
\| *	Merge pull request #671 from pafcu/master	jeroenpraat	2014-10-31	1	-1/+4
\| \|\ \| \| \| \| \| \|	Fix problem with default birth date
\| \| *	Fix problem with default birth date	Stefan Parviainen	2014-10-31	1	-1/+4
\| \| \|
\| * \|	Merge branch 'master' of https://github.com/friendica/red	marijus	2014-10-31	85	-3609/+3601
\| \|\ \
\| * \| \|	more work on photo upload	marijus	2014-10-31	5	-40/+41
\| \| \| \|
* \| \| \|	disable request message response until we work through this	friendica	2014-11-01	3	-2/+4
\| \| \| \|
* \| \| \|	doc updates	friendica	2014-11-01	10	-0/+1049
\| \|/ / \|/\| \|
* \| \|	document request packets a bit more	friendica	2014-10-31	1	-1/+4
\| \| \|
* \| \|	doc updates	friendica	2014-10-31	84	-3604/+3592
\| \| \|
* \| \|	flag notify packets that are sent in response to a message_id request and ↵	friendica	2014-10-31	1	-4/+5
\|/ / \| \| \| \| \| \|	prevent them from recursing
* \|	Heads up: "custom/module.php" is deprecated. Please read this commit if you ↵	friendica	2014-10-30	1	-1/+13
\| \| \| \| \| \| \| \|	are affected.
* \|	Merge https://github.com/friendica/red into pending_merge	friendica	2014-10-30	16	-429/+737
\|\ \
\| * \|	Debian doco - no longer uses dropbear.	Thomas Willingham	2014-10-31	1	-2/+2
\| \| \|
\| * \|	removing this was not a good idea...	marijus	2014-10-30	1	-0/+4
\| \| \|
\| * \|	update bootstrap library to version 3.3	marijus	2014-10-30	8	-333/+660
\| \| \|
\| * \|	some work on photo upload	marijus	2014-10-30	7	-97/+74
\| \| \|
* \| \|	What this checkin does is catch the case where a comment arrived and there's ↵	friendica	2014-10-30	8	-23/+180
\| \| \| \| \| \| \| \| \| \| \| \|	a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.