aboutsummaryrefslogtreecommitdiffstats
path: root/version.inc
Commit message (Collapse)AuthorAgeFilesLines
* prevent zid's from reaching the DAV core code.friendica2014-01-161-1/+1
|
* dav: throw exception if channel for requested DAV directory is deletedfriendica2014-01-151-1/+1
|
* mod_attach: output stream wasn't workingfriendica2014-01-111-1/+1
|
* directory creation error, display localtimes on cloud webpage, doc updatesfriendica2014-01-101-1/+1
|
* fix table bbcodefriendica2014-01-091-1/+1
|
* keep the to-do list somewhat current.friendica2014-01-081-1/+1
|
* make storage limit service classes apply to accounts, not channels. Also ↵friendica2014-01-071-2/+1
| | | | include a css file that was missing from work yesterday.
* version updatefriendica2014-01-061-4/+1
|
* Merge branch 'master' into movejsfriendica2014-01-061-0/+4
|\ | | | | | | | | Conflicts: version.inc
| * whitespacefriendica2014-01-061-1/+1
| |
| * the web browser interface for DAV has now got zotfriendica2014-01-051-1/+1
| |
* | move js files from corefriendica2014-01-041-1/+1
|/
* more dav workfriendica2014-01-031-1/+1
|
* some DAV tweaks before the next round of heavy liftingfriendica2014-01-021-1/+1
|
* return to working on red-dav; This is a bit of a slog at the moment and the ↵friendica2014-01-011-1/+1
| | | | basic framework isn't even close to working. This does break the working test we did have (which was never connected to the Red backend). Now we're starting to connect Red and DAV together intimately. There will probably be some twists and turns along the way as we get the information we need into all the class objects that need them. But the important part is that the RedDirectory and RedFile classes are loading without throwing white screens and from here we can use logging to figure out what the DAV front end is trying to do and what it is passing to the backend and hopefully figure out what it expects to do with the results. Unless you're a competent developer with a strong background in OOP and are helping develop this code, you should keep it an arm's length away from any production site and don't even think of enabling it. By default it is turned off.
* basic edit and delete for thingsfriendica2013-12-301-1/+1
|
* display_thing: it ain't much, but it's implemented.friendica2013-12-291-1/+1
|
* things can now have (consistent sized) photos - plus I found a couple of ↵friendica2013-12-281-1/+1
| | | | issues with duplicate notifications and contact photos not getting an album name (it was crossed with filename). The last one doesn't matter as neither is used, but it was wrong so it has been corrected. Oh and thing photos weren't working at all because the form element name was different than what the module was looking for. But that had never been tested as I was waiting to get the import/resize finished. Next up for that module is display and deletion of things; but the priority is pretty low.
* 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.
* issue #230 - deletion failure in multiple delivery chainsfriendica2013-12-261-1/+1
|
* use colorbox for single photo viewing (replacing prettyPhoto, which may have ↵friendica2013-12-251-1/+1
| | | | license incompatibilities). Also set maximum size of a directory popup and let it scroll after that in case somebody set their profile keywords to the content of Webster's dictionary.
* oopsfriendica2013-12-231-1/+1
|
* appears that I missed a few files for Comanchification. so here's mitem.friendica2013-12-221-1/+1
|
* split private messages into two modules - "message" is just for message ↵friendica2013-12-211-1/+1
| | | | lists, "mail" is for reading and writing conversations. This is so we can Comanchify it cleanly.
* comanchify mod_search - we've got three modules left to Comanchify: admin, ↵friendica2013-12-201-1/+1
| | | | directory and message - each of which introduces "interesting challenges"
* more comanche migrationfriendica2013-12-191-1/+1
|
* authtest: do a better job of success/failure indicationfriendica2013-12-171-1/+1
|
* install redbasic during setup so that at least one theme is registered. ↵friendica2013-12-161-1/+1
| | | | Otherwise none of the display settings seem to work very well.
* Provide a fallback channel to probe for magic-auth when we have no prior ↵friendica2013-12-151-1/+1
| | | | | | | | communications with a site. This will be a system channel if one exists, otherwise any channel will do. We'll try to use the first valid channel on the site because that was probably created when the site was installed and is the closest thing to a system channel we've got.
* a couple more comanche conversionsfriendica2013-12-141-1/+1
|
* add construct_page hookfriendica2013-12-131-1/+1
|
* check that every invocation of htmlspecialchars has the right arg listfriendica2013-12-121-1/+1
|
* comanchify all the simple cases - those that only load a profile. Rework ↵friendica2013-12-111-1/+1
| | | | permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using.
* we're almost ready to turn on comanche for mod_network. All the widgets are ↵friendica2013-12-101-1/+1
| | | | done.
* migrate follow widget to comanche and remove obsolete mod/intro.phpfriendica2013-12-091-1/+1
|
* starting on the journey to comanche everywhere - beginning with widget ↵friendica2013-12-081-1/+1
| | | | conversions. There are approximately 20 which need to be wrapped for accessibility to comanche.
* make suggestion photo sizes match top level post sizesfriendica2013-12-071-1/+1
|
* some code cleanup - gad I forgot what a mess the "other" notifications tabs ↵friendica2013-12-061-1/+1
| | | | (everything but system) were in. Maybe I'll just remove them so we can start over.
* mod_authtest --- magic-auth diagnostic for those that are too freaking ↵friendica2013-12-051-1/+1
| | | | important to read logs or code and expect others to be able to debug complex authentication transactions with no information beyond "it didn't work". This will provide a transaction report including both sides of the exchange that you can paste into a bug report and that a developer can actually figure out where in the transaction that things went wrong and maybe even be able to then figure out why.
* include re-organisation and more doco, post_to_red fix ampersands in categoriesfriendica2013-12-041-1/+1
|
* rev updatefriendica2013-12-031-1/+1
|
* refactor magic-authfriendica2013-12-021-1/+1
|
* deprecate a->get_curl_code() and $a->get_curl_headers()friendica2013-12-011-1/+1
|
* hooks getting called twicefriendica2013-11-301-1/+1
|
* allow zot-info to return results for address= with webbies or naked nicknamesfriendica2013-11-291-1/+1
|
* synchronise deletion of comments between red and wpfriendica2013-11-281-1/+1
|
* re-enable jquery migration tool until we sort out all the issuesfriendica2013-11-271-1/+1
|
* create jquery-compat to hold deprecated jquery functions, load it before all ↵friendica2013-11-261-1/+1
| | | | the dependent js scripts
* force HTML notification mails to use predefined colours.friendica2013-11-251-1/+1
|
* add recipient name to the rest of the notification emailsfriendica2013-11-241-1/+1
|