aboutsummaryrefslogtreecommitdiffstats
path: root/mod/import.php
Commit message (Collapse)AuthorAgeFilesLines
* Bust out import_account() into a separate function to allow importing ↵ken restivo2015-11-101-3/+13
| | | | accounts by proxy, i.e. for admins to import a channel on behalf of a user.
* more work on import & sync of private mail and conversationsredmatrix2015-10-141-0/+6
|
* add plugin hooks to channel sync/import/exportredmatrix2015-09-231-0/+2
|
* sync likesredmatrix2015-09-101-0/+3
|
* menu import and syncredmatrix2015-09-081-0/+3
|
* work on event syncredmatrix2015-09-071-0/+7
|
* consolidate import_items/sync_itemsredmatrix2015-09-071-50/+4
|
* import and sync chatroomsredmatrix2015-09-031-0/+3
|
* profile import error #34redmatrix2015-09-031-3/+2
|
* start to modularise the clone import and sync functionsredmatrix2015-09-021-204/+30
|
* import appsredmatrix2015-09-011-0/+23
|
* initial work on obj import, rename import_profile_photo to ↵redmatrix2015-09-011-16/+29
| | | | import_xchan_photo to more accurately state its purpose.
* this is a bit harder than anticipated.redmatrix2015-08-311-14/+15
|
* mostly doc tweaks, some import/export workredmatrix2015-08-311-2/+19
|
* Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-261-1/+0
|\ | | | | | | | | Conflicts: mod/import.php
| * syntax error in last checkinredmatrix2015-08-261-4/+4
| |
| * import fixesredmatrix2015-08-261-1/+33
| |
* | import fixesredmatrix2015-08-261-2/+15
| |
* | resolve conflictredmatrix2015-08-111-56/+6
| |
* | Merge https://github.com/redmatrix/redmatrix into pending_mergeredmatrix2015-08-111-0/+51
|\| | | | | | | | | | | Conflicts: doc/history.md mod/import.php
| * convert abook_flags from hubzilla during cloningredmatrix2015-08-101-4/+30
| |
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-07-141-0/+1
|\| | | | | | | | | Conflicts: mod/import.php
| * fix import of group membersredmatrix2015-07-141-1/+1
| |
* | group fixes to importredmatrix2015-07-141-4/+14
| |
* | more stuff to resume failed importsredmatrix2015-07-141-1/+13
| |
* | log the import progressredmatrix2015-07-141-3/+9
| |
* | provide resumable imports if things go wrongredmatrix2015-07-141-285/+329
| |
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-07-141-0/+1
|\| | | | | | | | | Conflicts: mod/connedit.php
* | cleanup of import to allow cross-product import going one way. Note - ↵redmatrix2015-06-301-9/+4
| | | | | | | | items/content are not yet importable
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-301-0/+14
|\|
| * warn if export data file is from an incompatible project or if the DB ↵redmatrix2015-06-291-0/+14
| | | | | | | | version differs significantly from the current DB. This is to avoid people cloning a hubzilla channel back to red and potentially stuffing up the works. Hopefully we can migrate upwards someday. Downwards is always going to be an issue.
* | lots of work on clone/import from redmatrix to hubzilla (won't go back the ↵redmatrix2015-06-301-15/+61
| | | | | | | | other way)
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-211-4/+20
|\| | | | | | | | | | | Conflicts: include/items.php util/messages.po
| * import: Improve the descriptive text for this featureredmatrix2015-06-211-2/+2
| |
| * some diaspora import issues uncovered during dry-run testsredmatrix2015-06-211-6/+6
| |
| * automatically gunzip Diaspora export files if we're on a *nix systemredmatrix2015-06-191-0/+9
| |
| * very early attempt diaspora import from diaspora export file. Currently the ↵redmatrix2015-06-191-1/+8
| | | | | | | | json export has to be gunzipped prior to uploading and we're net yet adding connections (which should come soon) and we can't import items until they add guids to the export file - so consider it a work in progress. This first attempt should create a channel and get your profile details setup providing there isn't a nickname conflict on the server. That will also be handled later.
* | convert the abook fieldsredmatrix2015-06-141-2/+2
| |
* | Merge branch 'master' into tresfriendica2015-04-231-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * title missing sending to diaspora (which doesn't support titles but let's ↵friendica2015-02-091-1/+1
| | | | | | | | not go there).
* | that should take care of the bitfields in hublocfriendica2015-01-201-7/+5
|/
* mod/import: try ten times to create a unique webbie if the chosen one is in use.friendica2014-12-181-3/+27
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* fix import sql errorfriendica2014-10-131-1/+1
|
* disable email notifications when bulk importing content.friendica2014-10-081-0/+5
|
* optionally include wall items (posts) in import/exportfriendica2014-09-251-2/+55
|
* when importing channels - use the new location notification message to tell ↵friendica2014-09-161-9/+4
| | | | your original site where it sits in terms of primary.
* channel export with itemsfriendica2014-09-151-0/+6
|
* honour service class restrictions for total_identities, total_channels ↵friendica2014-09-151-1/+28
| | | | ("friends") and total_feeds both when importing channels and subsequently when syncing clones. Limits are based on the local system - additional entries are silently dropped.
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'