aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* fix private message encryption since the input_filter mangled itfriendica2013-09-031-2/+2
|
* add design tool menu to appropriate pagesfriendica2013-09-031-1/+17
|
* make displaying the language selector configurablefriendica2013-09-031-1/+1
|
* my badfriendica2013-09-031-1/+1
|
* typofriendica2013-09-031-1/+1
|
* personal config to just show the page content without author info - probably ↵friendica2013-09-031-3/+5
| | | | this needs to be a page option
* testing Comanchefriendica2013-09-031-6/+7
|
* add a layout selectorfriendica2013-09-022-0/+35
|
* The triple linebreaks in notification emails finally bothered me enough to ↵friendica2013-09-021-4/+2
| | | | do something about it.
* preserve mimetype on page editsfriendica2013-09-021-4/+5
|
* Merge pull request #108 from cvogeley/masterfriendica2013-09-021-0/+1
|\ | | | | More mobile theme fixes
| * More mobile theme fixesChristian Vogeley2013-08-311-0/+1
| | | | | | | | | | | | If user is logged in personal settings are used else use admin settings. Only show toggle link if there is something to switch between.
* | oh that's whyfriendica2013-09-022-2/+4
| |
* | pass execflag - Working for preview but not yet executing on page renderfriendica2013-09-021-0/+1
| |
* | fix webpage storagefriendica2013-09-022-2/+2
| |
* | only allow richtext editor on pages if bbcode is the default mimetype, ↵friendica2013-09-021-6/+6
| | | | | | | | otherwise use plaintext editor. This will eventually need work to support a visual editor for html or other types.
* | allow a channel owner to define a default mimetype on webpages (otherwise ↵friendica2013-09-022-4/+11
| | | | | | | | default to "choose") - also fix the selector w/r/t php code. There is no ui for setting either at the moment, but for instance with wiki pages we probably don't want to have multiple choice of the mimetype. Keep it simple.
* | webpage content-type -- needs cleaning up and a security check once all the ↵friendica2013-09-023-7/+71
| | | | | | | | important bits are in place.
* | Add Comanche layouts to the things that don't go offsite.friendica2013-09-011-0/+4
| |
* | Sheesh. Three lines of Javascript. All you have to do is find which of the ↵friendica2013-09-011-0/+11
| | | | | | | | three lines is doing something wrong. Or FILE A BUG. Or use a different browser (not *try* a different browser, *use* a different browser), or turn off freaking tinymce. But no - let's argue about browsers instead.
* | rework the pdl_selector a bit since we've slightly changed the way layouts ↵friendica2013-09-011-9/+3
|/ | | | are stored.
* more debugging on localize_item top find out why likes are not translated in ↵friendica2013-08-311-1/+7
| | | | notifications, but are in displayed posts (using 'new' on matrix page) - in one case we're successfully pulling stuff from item['object'] and in the other we aren't - and it's the same object.
* I've got a pretty good idea of how to bootstrap, parse and render Comanche ↵friendica2013-08-291-5/+22
| | | | now. This does not mean it's close to being presentable - far from it.
* figure out why poller isn't picking up old posts which failed to deliverfriendica2013-08-292-5/+6
|
* silence some warnings at php E_ALL levelsfriendica2013-08-282-1/+3
|
* really truly bare-bones comanchefriendica2013-08-282-0/+59
|
* It's a wretched mess, but at least photo comments show up again when viewing ↵friendica2013-08-281-0/+1
| | | | the photo. This is just temporary until these conversations are merged into the common conversation viewer, so it's not worth spending a lot of time cleaning up the remnants.
* right - here's how we're going to link comanche with webpagesfriendica2013-08-281-0/+48
|
* bring back mail list and cleanup some issues which popped out with full PHP ↵friendica2013-08-272-3/+3
| | | | warnings
* Preparatory work for photo conversations (third time). Also take away unused ↵friendica2013-08-271-7/+12
| | | | "post new activity" preferences until they actually do something.
* more loose endsfriendica2013-08-271-1/+4
|
* force webbies to lowercasefriendica2013-08-271-1/+1
|
* update hubloc_timestampsfriendica2013-08-271-5/+14
|
* when using the bbcode mimetype a space is just a space. A return is a ↵friendica2013-08-271-0/+1
| | | | return. But as opposed to HTML, two spaces are now non-breaking. A tab (assuming you can figure out how to enter one in a text field) is now four non-breaking spaces. This should let us insert code snippets with much more readable indentation.
* get rid of ssl_policy - it's implicit in the site urlfriendica2013-08-271-16/+16
|
* clone sync was trying to update xchan info in the abook loop.friendica2013-08-261-1/+1
|
* fix profile change activity where the change is a solitary url - and ↵friendica2013-08-262-1/+3
| | | | includes a stray right quote
* more cleanup from the mess yesterday - you might have a look for xchan_addr ↵friendica2013-08-261-0/+3
| | | | and hubloc_addr with slashes in them and fix them - especially getting rid of ip addresses and the /channel/xyz in the addr fields
* regex patchfriendica2013-08-261-1/+1
|
* try to fix bad addresses that got into the networkfriendica2013-08-251-0/+3
|
* Try to ensure full paths don't leak into xchan_addr and hubloc_addrfriendica2013-08-251-1/+1
|
* extra logging for translating likes in notification emails - which is still ↵friendica2013-08-221-0/+3
| | | | failing on occasion.
* possible fix for mention tags not posting to mentioned forum (when send ↵friendica2013-08-221-3/+25
| | | | stream permission is blocked)
* add detailed logging to public recips - find out why some public recipients ↵friendica2013-08-221-0/+3
| | | | are getting bypassed (David Benfells' problem with tagging groups, etc.)
* make premium channels a featurefriendica2013-08-221-2/+1
|
* add zid to connect_urlfriendica2013-08-221-1/+1
|
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-212-2/+14
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* progress on generic sellpage - is not yet linked from existing connect ↵friendica2013-08-211-1/+2
| | | | buttons and editing has not been completed
* implement premium channel discoveryfriendica2013-08-211-5/+14
|
* fix superblock for commentsfriendica2013-08-202-2/+16
|