| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
install/schema_mysql.sql
mod/home.php
mod/page.php
view/nl/messages.po
view/nl/strings.php
|
| |
| |
| |
| | |
webpages to be viewed even if site is configured "block public".
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
install/schema_mysql.sql
mod/impel.php
view/pt-br/messages.po
view/pt-br/strings.php
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
view/nl/messages.po
view/nl/strings.php
|
| | |
|
| | |
|
| |
| |
| |
| | |
migration tools, and only for mysql currently. Oh, and you still don't have the new code to make use of the new schema yet. That's on another branch that I'm not checking in yet because then you might get the idea that bits of it actually work and infect the rest of the matrix with unstable code and bring other sites down that have never even heard of hubzilla. Please do not use this code. Let me repeat, please do not use this code. One more time in case you didn't understand - please do not use this code.
|
|\| |
|
| |
| |
| |
| | |
clients, which will be extended in the future to allow specific permissions.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
queries.
|
| |
|
|
|
|
| |
that is where the dir is created, change install doc to point to install/schema_xxxxx.sql instead of database.sql
|
|
|
|
| |
added retro-actively to existing DBs as an update. It isn't clear if this helps sites any more than just restricting the abook table to certain channel_id's is (and this field is already indexed).
|
| |
|
|
|
|
| |
in a couple of places like the group list widget and saved search term widget and ignoring friend suggestions where it was more appropriate to leave it.
|
|
|
|
| |
- change PRIMARY_KEY to PRIMARY KEY
- replace smallint(1) with smallint
|
|
|
|
| |
if the realm is so configured.
|
| |
|
|
|
|
| |
(although it shouldn't break anything on existing sites.)
|
| |
|
|
|
|
| |
searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
digital signature with ratings so that directories can pass them around, second provide some directory registration functions so we can obtain a list of directories from somewhere (to pass ratings around between them). This gives the primary directory role some value as that is where you register your directory.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
statement-locked.
FWIW, the exact same queries listed for postgres are perfectly valid and equivalent on mysql. no need for separate
statements.
|
|
|
|
| |
xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
it isn't a directory server any more.
|
| |
|
| |
|
| |
|
|
|
|
| |
add rudimentary resume
|
|
|
|
| |
provided with the WorksForMe(tm) warranty of fitness for a purpose implied or otherwise
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
boot.php
include/dba/dba_driver.php
include/diaspora.php
include/follow.php
include/session.php
include/zot.php
mod/photos.php
mod/ping.php
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|