aboutsummaryrefslogtreecommitdiffstats
path: root/doc/html/taxonomy_8php.html
Commit message (Collapse)AuthorAgeFilesLines
* doc updatesfriendica2014-12-191-3/+55
|
* doc updatesfriendica2014-11-071-1/+55
|
* doc updates and a couple of issues spotted in the logs (diaspora likes, feed ↵friendica2014-09-121-1/+1
| | | | author import)
* doc updatesfriendica2014-07-041-1/+1
|
* doc updates, plus back-end work for rpost to let you post to a different ↵friendica2014-04-041-1/+1
| | | | channel than your current logged-in channel. Need the same for rbmark back-end. Then we "just" need a selector widget on the editor forms.
* doc updatesfriendica2014-02-071-1/+1
|
* doc updatesfriendica2014-01-031-5/+36
|
* sslify - remove the redirect fallback - as it gets called occasionally and ↵friendica2013-12-271-1/+1
| | | | creates mixed content exceptions. Let's see how we go without it. Also a doc update.
* add construct_page hookfriendica2013-12-131-3/+1
|
* doc updatesfriendica2013-12-061-1/+1
|
* doc updatesfriendica2013-11-281-1/+1
|
* doc updatesfriendica2013-11-021-7/+19
|
* doc updatesfriendica2013-10-261-2/+2
|
* doc updatesfriendica2013-10-181-1/+1
|
* doc updatesfriendica2013-09-201-0/+50
|
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-131-2/+2
| | | | posts have recipients.
* provide mimetype selector on edit (pages and blocks)friendica2013-09-061-1/+1
|
* issue #82, posted order not working - also doc updatefriendica2013-08-171-1/+1
|
* move sitekey creation to the account creation function instead of during ↵friendica2013-08-091-2/+2
| | | | channel creation. Channel import bypassed sitekey creation completely. We should do it during install, but it's possible somebody might have to install manually and the sitekey would never get created. This is the best compromise I can come up with. Looks like the doc tree was also updated in this checkin
* basic email invitations - and doc updatefriendica2013-08-021-1/+1
|
* Add self to recipient lists. Sure we already have a copy but it's possible ↵friendica2013-07-141-1/+1
| | | | our nomadic channel clones don't.
* use current channel photo for favicon where applicable - might be browser ↵friendica2013-07-071-8/+73
| | | | dependent but seems to work on FF
* doc update, plus possible fix to "complex delivery chains" issue. Basically ↵friendica2013-06-291-0/+104
| | | | when the top-level post creator replies to a thread he sent to a forum via tags, it isn't getting redelivered to the forum members.
* upgrade docofriendica2013-06-211-0/+331