aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* more loggingfriendica2013-09-151-0/+3
|
* don't create a directory sync notification (entry in the updates table) if ↵friendica2013-09-151-17/+30
| | | | the site record was updated - without checking first to see if anything changed. This is causing lots of sync entries when nothing changed to warrant it.
* implement what I hope will now be the server side of directory sync, add ↵friendica2013-09-152-13/+24
| | | | viewsrc to item_photo_menu, and log what changed in import_xchan update objects so we can find out why there are so many updates when nothing _obvious_ has changed that should trigger it.
* some fixes to directory keyword searchesfriendica2013-09-141-1/+1
|
* set menu_channel_id before we use it in a queryMichael Johnston2013-09-141-3/+2
|
* let me edit menu_desc even if menu_name has not changedMichael Johnston2013-09-141-2/+4
|
* Revert broken commitOlaf Conradi2013-09-141-92/+2
|
* First try to tell a comment from a like/dislike in notification systemmrjive2013-09-141-2/+92
|
* import_xchan - check every known hubloc/location field and create a new ↵friendica2013-09-141-4/+8
| | | | hubloc if anything at all changed anywhere.
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-132-0/+7
| | | | posts have recipients.
* need to figure out what's causing thisfriendica2013-09-121-0/+6
|
* No point beating a dead horsefriendica2013-09-121-1/+8
|
* so public_recips and allowed_public_recips is working so much better than ↵friendica2013-09-121-4/+12
| | | | before, but was still not quite right. We seem to be getting all the right results for top-level posts now, but comments aren't getting through on channels for which we've allowed them to send us their stream, but not comment on our posts. The reason is we were seeing if they could comment - and we only need to do that if we own the post. If they own the post, we only need to check if they can send us their stream.
* remove some debugging stuff now that the problem they were trying to locate ↵friendica2013-09-121-5/+0
| | | | down has been solved.
* Merge pull request #129 from MicMee/masterfriendica2013-09-121-1/+2
|\ | | | | to flag failed auth attempts in db table hubloc as hubloc_receive_error
| * delete logger line; was the wrong place.Michael Meer2013-09-111-1/+0
| |
| * flag failed auth attempts in DB table hublocMichael Meer2013-09-111-1/+3
| |
* | assuming this doesn't blow up the internet like the last fix - this is a ↵friendica2013-09-111-1/+1
|/ | | | very old bug that's been reported time and time again and nobody every bothered to debug or even report it somewhere where we could monitor it. It's buried somewhere in my stream, but basically is "things don't work right if you've got 'everybody in my address book' permissions" on "can send me their channel stream and posts". I think this is Michelle's problem and anybody else who has en empty matrix after making lots of connections.
* make comments work againfriendica2013-09-101-1/+2
|
* well that really stuffed things up...friendica2013-09-102-3/+3
|
* this should fix the foreign language like notifications (again)friendica2013-09-101-2/+4
|
* change wording on item_store message so we can find failures fast with grep ↵friendica2013-09-101-1/+1
| | | | item_store logfile | grep -v created
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-105-27/+60
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* z_fetch_url - include curl debug info in return array and log it (at ↵friendica2013-09-101-0/+10
| | | | | | logger_data level) on failure This should probably be at a lower log level, but unsuccessful connections could happen a lot on a busy production site so we'll try to keep the log noise down unless somebody really needs to track this info.
* just a typoMichael Meer2013-09-091-1/+1
|
* some alteration to the way directory sync was originally supposed to work. ↵friendica2013-09-091-25/+14
| | | | I'm making this up as I go and not exactly certain where to go next but it makes more sense now and I think the basic idea will actually work. I'll just have to keep making it up until it does work.
* perform a refresh_all when an import has completed so that all your ↵friendica2013-09-081-3/+2
| | | | connections get a fresh update.
* make sure new contacts who are not yet in the address book are sync'd across ↵friendica2013-09-081-0/+14
| | | | clone instances
* Merge pull request #119 from unary/categorywidgetfriendica2013-09-081-2/+9
|\ | | | | only show categories this channel has used
| * added dbescMichael Johnston2013-09-081-1/+1
| |
| * only show categories this channel has usedMichael Johnston2013-09-081-2/+9
| |
* | Merge service classChristian Vogeley2013-09-084-12/+35
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | //service class configure in .htconfig.php: $a->config['system']['default_service_class']='standard'; // this is the default service class that is attached to every new account $a->config['service_class']['standard'] = array('photo_upload_limit'=>20000000, // total photo storage limit per channel (here 20MB) 'total_identities' =>5, // number of channels an account can create 'total_items' =>2000, // number of top level posts a channel can create. Applies only to top level posts of the user, other posts and comments are unaffected 'total_pages' =>10, // number of pages a channel can create 'total_channels' =>500, // number of channels the user can add, other users can still add this channel, even if the limit is reached 'attach_upload_limit' =>20000000); // total attachment storage limit per channel (here 20MB)
| * Service class itemsChristian Vogeley2013-09-081-1/+1
| | | | | | | | Items / webpages /attachment message
| * Service classChristian Vogeley2013-09-083-11/+34
| | | | | | | | identity, follow, photo upload, att upload
* | encode and decode channel names containing HTML special characters and ↵friendica2013-09-061-21/+1
| | | | | | | | quotes so they will survive a reshare without mangling
* | public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-051-3/+16
| | | | | | | | updated their site access policy which old sites do not have)
* | pages feedfriendica2013-09-051-15/+29
| |
* | issue #59 - this is a real bugger. Might seem fixed but read the code. This ↵friendica2013-09-041-2/+7
| | | | | | | | could potentially create a security/permissions issue
* | provide templating options in comanche for the underlying webpage element - ↵friendica2013-09-042-0/+33
| | | | | | | | in this case the way the author is displayed. Leave this open for other forms templating options.
* | render blocks - yes these should be templates, but I've got too much to do ↵friendica2013-09-041-0/+23
| | | | | | | | at the moment and just want everything to fall into place quickly. The clerical work will have to wait.
* | 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
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 04:04:03 +0000