-
Notifications
You must be signed in to change notification settings - Fork 672
/
admin.pot
2142 lines (1615 loc) · 76.3 KB
/
admin.pot
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2013, Various
# This file is distributed under the same license as the Elgg package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Elgg master\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-04-24 13:13+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../admin/backup-restore.rst:2
msgid "Backup and Restore"
msgstr ""
#: ../../admin/backup-restore.rst:6
#: ../../admin/composer.rst:9
#: ../../admin/cron.rst:6
#: ../../admin/duplicate-installation.rst:6
#: ../../admin/getting-help.rst:10
#: ../../admin/performance.rst:8
#: ../../admin/plugins.rst:8
#: ../../admin/security.rst:8
#: ../../admin/upgrading.rst:11
#: ../../admin/uservalidation.rst:8
msgid "Contents"
msgstr ""
#: ../../admin/backup-restore.rst:9
#: ../../admin/duplicate-installation.rst:9
msgid "Introduction"
msgstr ""
#: ../../admin/backup-restore.rst:12
msgid "Why"
msgstr ""
#: ../../admin/backup-restore.rst:14
msgid "Shared hosting providers typically don't provide an automated way to backup your Elgg installation. This article will address a method of accomplishing this task."
msgstr ""
#: ../../admin/backup-restore.rst:16
msgid "In IT there are often many ways to accomplish the same thing. Keep that in mind. This article will explain one method to backup and restore your Elgg installation on a shared hosting provider that uses the CPanel application. However, the ideas presented here can be tailored to other applications as well. The following are typical situations that might require a procedure such as this:"
msgstr ""
#: ../../admin/backup-restore.rst:18
msgid "Disaster Recovery"
msgstr ""
#: ../../admin/backup-restore.rst:19
msgid "Moving your Elgg site to a new host"
msgstr ""
#: ../../admin/backup-restore.rst:20
msgid "Duplicating an installation"
msgstr ""
#: ../../admin/backup-restore.rst:23
msgid "What"
msgstr ""
#: ../../admin/backup-restore.rst:25
msgid "Topics covered:"
msgstr ""
#: ../../admin/backup-restore.rst:27
msgid "Full backups of the Elgg directories and MySQL databases are performed daily (automated)"
msgstr ""
#: ../../admin/backup-restore.rst:28
msgid "The backups are sent to an off-site location via FTP (automated)"
msgstr ""
#: ../../admin/backup-restore.rst:29
msgid "The local backups are deleted after successful transfer to the off-site location (automatic)"
msgstr ""
#: ../../admin/backup-restore.rst:30
msgid "Five days of backups will be maintained (automated)"
msgstr ""
#: ../../admin/backup-restore.rst:31
msgid "Restoration of data to the new host (manual)"
msgstr ""
#: ../../admin/backup-restore.rst:33
msgid "This process was composed with assistance from previous articles in the Elgg documentation wiki."
msgstr ""
#: ../../admin/backup-restore.rst:36
msgid "Assumptions"
msgstr ""
#: ../../admin/backup-restore.rst:38
msgid "The following assumptions have been made:"
msgstr ""
#: ../../admin/backup-restore.rst:40
msgid "The Elgg program directory is ``/home/userx/public_html``"
msgstr ""
#: ../../admin/backup-restore.rst:41
msgid "The Elgg data directory is ``/home/userx/elggdata``"
msgstr ""
#: ../../admin/backup-restore.rst:42
msgid "You've created a local directory for your backups at ``/home/userx/sitebackups``"
msgstr ""
#: ../../admin/backup-restore.rst:43
msgid "You have an off-site FTP server to send the backup files to"
msgstr ""
#: ../../admin/backup-restore.rst:44
msgid "The directory that you will be saving the off-site backups to is ``/home/usery/sitebackups/``"
msgstr ""
#: ../../admin/backup-restore.rst:45
msgid "You will be restoring the site to a second shared hosting provider in the ``/home/usery/public_html`` directory"
msgstr ""
#: ../../admin/backup-restore.rst:49
msgid "Be sure to replace ``userx``, ``usery``, ``http://mynewdomain.com`` and all passwords with values that reflect your actual installation!"
msgstr ""
#: ../../admin/backup-restore.rst:52
msgid "Creating a usable backup - automatically"
msgstr ""
#: ../../admin/backup-restore.rst:55
msgid "Customize the backup script"
msgstr ""
#: ../../admin/backup-restore.rst:57
msgid "The script that you will use can be found :doc:`here <backup/ftp-backup-script>` ."
msgstr ""
#: ../../admin/backup-restore.rst:59
msgid "Just copy the script to a text file and name the file with a .pl extension. You can use any text editor to update the file."
msgstr ""
#: ../../admin/backup-restore.rst:61
msgid "Change the following to reflect your directory structure:"
msgstr ""
#: ../../admin/backup-restore.rst:71
msgid "Change the following to reflect your database parameters:"
msgstr ""
#: ../../admin/backup-restore.rst:82
msgid "Change the following to reflect your off-site FTP server parameters:"
msgstr ""
#: ../../admin/backup-restore.rst:92
msgid "Save the file with the ``.pl`` extension (for the purposes of this article we will name the file: ``elgg-ftp-backup-script.pl``) and upload it to the following directory ``/home/userx/sitebackups``"
msgstr ""
#: ../../admin/backup-restore.rst:94
msgid "Be aware that you can turn off FTP and flip a bit in the script so that it does not delete the local backup file in the event that you don't want to use off-site storage for your backups."
msgstr ""
#: ../../admin/backup-restore.rst:97
msgid "Configure the backup Cron job"
msgstr ""
#: ../../admin/backup-restore.rst:99
msgid "Login to your CPanel application and click on the \"Cron Jobs\" link. In the Common Settings dropdown choose \"Once a day\" and type the following in the command field ``/usr/bin/perl /home/userx/sitebackups/elgg-ftp-backup-script.pl``"
msgstr ""
#: ../../admin/backup-restore.rst:101
msgid "Click on the \"Add New Cron Job\" button. Daily full backups are now scheduled and will be transferred off-site."
msgstr ""
#: ../../admin/backup-restore.rst:104
msgid "Configure the cleanup Cron job"
msgstr ""
#: ../../admin/backup-restore.rst:106
msgid "If you are sending your backups, via FTP, to another shared hosting provider that uses the CPanel application or you've turned off FTP altogether you can configure your data retention as follows."
msgstr ""
#: ../../admin/backup-restore.rst:108
msgid "Login to your CPanel application for your FTP site, or locally if you're not using FTP, and click on the \"Cron Jobs\" link. In the Common Settings dropdown choose \"Once a day\" and type the following in the command field ``find /home/usery/sitebackups/full_* -mtime +4 -exec rm {} \\;``"
msgstr ""
#: ../../admin/backup-restore.rst:110
msgid "The ``-mtime X`` parameter will set the number of days to retain backups. All files older than ``x`` number of days will be deleted. Click on the \"Add New Cron Job\" button. You have now configured your backup retention time."
msgstr ""
#: ../../admin/backup-restore.rst:113
msgid "Restoring from backup"
msgstr ""
#: ../../admin/backup-restore.rst:116
msgid "Prepare your backup files"
msgstr ""
#: ../../admin/backup-restore.rst:118
msgid "The assumption is that you're restoring your site to another shared hosting provider with CPanel."
msgstr ""
#: ../../admin/backup-restore.rst:120
msgid "When the script backed the files up the original directory structure was maintained in the zip file. We need to do a little cleanup. Perform the following:"
msgstr ""
#: ../../admin/backup-restore.rst:122
msgid "Download the backup file that you wish to restore from"
msgstr ""
#: ../../admin/backup-restore.rst:123
msgid "Extract the contents of the backup file"
msgstr ""
#: ../../admin/backup-restore.rst:127
msgid "Drill down and you will find your site backup and SQL backup. Extract both of these. You will then have:"
msgstr ""
#: ../../admin/backup-restore.rst:125
msgid "a MySQL dump file with a ``.sql`` extension"
msgstr ""
#: ../../admin/backup-restore.rst:127
msgid "another directory structure with the contents of:"
msgstr ""
#: ../../admin/backup-restore.rst:127
msgid "``/home/userx/public_html``"
msgstr ""
#: ../../admin/backup-restore.rst:128
msgid "``/home/userx/elggdata``"
msgstr ""
#: ../../admin/backup-restore.rst:129
msgid "Repackage the contents of the ``/home/userx/public_html`` directory as a zip file so that the files are in the root of the zip file"
msgstr ""
#: ../../admin/backup-restore.rst:130
msgid "The reason for doing this is simple. It's much more efficient to upload one zip file than it is to ftp the contents of the ``/home/userx/public_html`` directory to your new host."
msgstr ""
#: ../../admin/backup-restore.rst:131
msgid "Repackage the contents of the /home/userx/elggdata directory as a zip file so that the files are in the root of the zip file"
msgstr ""
#: ../../admin/backup-restore.rst:133
msgid "You should now have the following files:"
msgstr ""
#: ../../admin/backup-restore.rst:135
msgid "the ``.sql`` file"
msgstr ""
#: ../../admin/backup-restore.rst:136
msgid "the zip file with the contents of ``/home/userx/public_html`` in the root"
msgstr ""
#: ../../admin/backup-restore.rst:137
msgid "the zip file with the contents of ``/home/userx/elggdata`` in the root"
msgstr ""
#: ../../admin/backup-restore.rst:140
msgid "Restore the files"
msgstr ""
#: ../../admin/backup-restore.rst:142
msgid "This is written with the assumption that you're restoring to a different host but maintaining the original directory structure. Perform the following:"
msgstr ""
#: ../../admin/backup-restore.rst:144
msgid "Login to the CPanel application on the host that you wish to restore the site to and open the File Manager."
msgstr ""
#: ../../admin/backup-restore.rst:148
msgid "Navigate to ``/home/usery/public_html``"
msgstr ""
#: ../../admin/backup-restore.rst:146
msgid "Upload the zip file that contains the ``/home/userx/public_html`` files"
msgstr ""
#: ../../admin/backup-restore.rst:147
#: ../../admin/backup-restore.rst:152
msgid "Extract the zip file"
msgstr ""
#: ../../admin/backup-restore.rst:148
msgid "You should now see all of the files in ``/home/usery/public_html``"
msgstr ""
#: ../../admin/backup-restore.rst:149
#: ../../admin/backup-restore.rst:154
msgid "Delete the zip file"
msgstr ""
#: ../../admin/backup-restore.rst:154
msgid "Navigate to ``/home/usery/elggdata``"
msgstr ""
#: ../../admin/backup-restore.rst:151
msgid "Upload the zip file that contains the ``/home/userx/elggdata`` files"
msgstr ""
#: ../../admin/backup-restore.rst:153
msgid "You should now see all of the files in /home/usery/elggdata"
msgstr ""
#: ../../admin/backup-restore.rst:156
msgid "Program and data file restoration is complete"
msgstr ""
#: ../../admin/backup-restore.rst:159
msgid "Restore the MySQL Database"
msgstr ""
#: ../../admin/backup-restore.rst:163
msgid "Again, the assumption here is that you're restoring your Elgg installation to a second shared hosting provider. Each shared hosting provider prepends the account holder's name to the databases associated with that account. For example, the username for our primary host is ``userx`` so the host will prepend ``userx_`` to give us a database name of ``userx_elgg``. When we restore to our second shared hosting provider we're doing so with a username of ``usery`` so our database name will be ``usery_elgg``. The hosting providers don't allow you to modify this behavior. So the process here isn't as simple as just restoring the database from backup to the usery account. However, having said that, it's not terribly difficult either."
msgstr ""
#: ../../admin/backup-restore.rst:166
msgid "Edit the MySQL backup"
msgstr ""
#: ../../admin/backup-restore.rst:168
msgid "Open the ``.sql`` file that you extracted from your backup in your favorite text editor. Comment out the following lines with a hash mark:"
msgstr ""
#: ../../admin/backup-restore.rst:175
msgid "Save the file."
msgstr ""
#: ../../admin/backup-restore.rst:178
msgid "Create the new database"
msgstr ""
#: ../../admin/backup-restore.rst:180
msgid "Perform the following:"
msgstr ""
#: ../../admin/backup-restore.rst:189
msgid "Login to the CPanel application on the new host and click on the \"MySQL Databases\" icon"
msgstr ""
#: ../../admin/backup-restore.rst:183
msgid "Fill in the database name and click the \"create\" button. For our example we are going to stick with ``elgg`` which will give us a database name of ``usery_elgg``"
msgstr ""
#: ../../admin/backup-restore.rst:185
msgid "You can associate an existing user with the new database, but to create a new user you will need to:"
msgstr ""
#: ../../admin/backup-restore.rst:185
msgid "Go to the \"Add New User\" section of the \"MySQL Databases\" page"
msgstr ""
#: ../../admin/backup-restore.rst:186
msgid "Enter the username and password. For our example we're going to keep it simple and use ``elgg`` once again. This will give us a username of ``usery_elgg``"
msgstr ""
#: ../../admin/backup-restore.rst:189
msgid "Associate the new user with the new database"
msgstr ""
#: ../../admin/backup-restore.rst:188
msgid "Go to the \"Add User To Database\" section of the \"MySQL Databases\" page. Add the ``usery_elgg`` user to the ``usery_elgg`` database"
msgstr ""
#: ../../admin/backup-restore.rst:189
msgid "Select \"All Privileges\" and click the \"Make Changes\" button"
msgstr ""
#: ../../admin/backup-restore.rst:192
msgid "Restore the production database"
msgstr ""
#: ../../admin/backup-restore.rst:194
msgid "Now it's time to restore the MySQL backup file by importing it into our new database named \"usery_elgg\"."
msgstr ""
#: ../../admin/backup-restore.rst:200
msgid "Login to the CPanel application on the new host and click on the \"phpMyAdmin icon"
msgstr ""
#: ../../admin/backup-restore.rst:197
msgid "Choose the ``usery_elgg`` database in the left hand column"
msgstr ""
#: ../../admin/backup-restore.rst:198
msgid "Click on the \"import\" tab at the top of the page"
msgstr ""
#: ../../admin/backup-restore.rst:199
msgid "Browse to the ``.sql`` backup on your local computer and select it"
msgstr ""
#: ../../admin/backup-restore.rst:200
msgid "Click the \"Go\" button on the bottom right side of the page"
msgstr ""
#: ../../admin/backup-restore.rst:202
msgid "You should now see a message stating that the operation was successful"
msgstr ""
#: ../../admin/backup-restore.rst:205
msgid "Bringing it all together"
msgstr ""
#: ../../admin/backup-restore.rst:207
msgid "The restored elgg installation knows **nothing** about the new database name, database username, directory structure, etc. That's what we're going to address here."
msgstr ""
#: ../../admin/backup-restore.rst:209
msgid "Edit ``/public_html/elgg-config/settings.php`` on the new hosting provider to reflect the database information for the database that you just created."
msgstr ""
#: ../../admin/backup-restore.rst:231
msgid "Upload the ``settings.php`` file back to the new host - overwriting the existing file."
msgstr ""
#: ../../admin/backup-restore.rst:233
msgid "Open the phpMyAdmin tool on the new host from the CPanel. Select the ``usery_elgg`` database on the left and click the SQL tab on the top of the page. Run the following SQL queries against the ``usery_elgg`` database:"
msgstr ""
#: ../../admin/backup-restore.rst:235
#: ../../admin/duplicate-installation.rst:175
msgid "Change the installation path"
msgstr ""
#: ../../admin/backup-restore.rst:241
#: ../../admin/duplicate-installation.rst:182
msgid "Change the data directory"
msgstr ""
#: ../../admin/backup-restore.rst:247
msgid "Change the filestore data directory"
msgstr ""
#: ../../admin/backup-restore.rst:254
msgid "Finalizing the new installation"
msgstr ""
#: ../../admin/backup-restore.rst:256
msgid "Run the upgrade script by visiting the following URL: ``http://mynewdomain.com/upgrade.php`` . Do this step twice - back to back."
msgstr ""
#: ../../admin/backup-restore.rst:258
msgid "Update your DNS records so that your host name resolves to the new host's IP address if this is a permanent move."
msgstr ""
#: ../../admin/backup-restore.rst:261
msgid "Congratulations!"
msgstr ""
#: ../../admin/backup-restore.rst:263
msgid "If you followed the steps outlined here you should now have a fully functional copy of your primary Elgg installation."
msgstr ""
#: ../../admin/backup-restore.rst:266
#: ../../admin/duplicate-installation.rst:231
msgid "Related"
msgstr ""
#: ../../admin/backup/ftp-backup-script.rst:2
msgid "FTP backup script"
msgstr ""
#: ../../admin/backup/ftp-backup-script.rst:4
msgid "Here is an automated script for backing up an Elgg installation."
msgstr ""
#: ../../admin/composer.rst:2
msgid "Composer installation"
msgstr ""
#: ../../admin/composer.rst:4
msgid "The easiest way to keep your Elgg site up-to-date is by using `Composer`_. Composer will take care of installing all the required dependencies of all plugins and Elgg, while also keeping those depencies up-to-date without having conflicts."
msgstr ""
#: ../../admin/composer.rst:12
msgid "Install Composer"
msgstr ""
#: ../../admin/composer.rst:14
msgid "https://getcomposer.org/download/"
msgstr ""
#: ../../admin/composer.rst:17
msgid "Install Elgg as a Composer Project"
msgstr ""
#: ../../admin/composer.rst:26
msgid "This will create a composer.json file based of the `Elgg starter project`_ which has the basics of installing Elgg."
msgstr ""
#: ../../admin/composer.rst:29
msgid "Open your browser"
msgstr ""
#: ../../admin/composer.rst:31
msgid "Go to your browser and install Elgg via the installation interface"
msgstr ""
#: ../../admin/composer.rst:34
msgid "Setup version controls"
msgstr ""
#: ../../admin/composer.rst:36
msgid "This step is optional but highly recommended. It'll allow you to easily manage the installation of the same plugin versions between environments (development/testing/production)."
msgstr ""
#: ../../admin/composer.rst:50
msgid "Install plugins"
msgstr ""
#: ../../admin/composer.rst:52
msgid "Install plugins as Composer depencies. This assumes that a plugin has been registered on `Packagist`_"
msgstr ""
#: ../../admin/composer.rst:61
msgid "Commit"
msgstr ""
#: ../../admin/composer.rst:63
msgid "Make sure ``composer.lock`` is not ignored in ``.gitignore``"
msgstr ""
#: ../../admin/composer.rst:72
msgid "Deploy to production"
msgstr ""
#: ../../admin/composer.rst:75
msgid "Initial Deploy"
msgstr ""
#: ../../admin/composer.rst:89
msgid "Subsequent Deploys"
msgstr ""
#: ../../admin/cron.rst:2
msgid "Cron"
msgstr ""
#: ../../admin/cron.rst:9
msgid "What does it do?"
msgstr ""
#: ../../admin/cron.rst:11
msgid "`Cron`_ is a program available on Unix-based operating systems that enables users to run commands and scripts at set intervals or at specific times."
msgstr ""
#: ../../admin/cron.rst:14
msgid "Elgg's cron handler allows administrators and plugin developers to setup jobs that need to be executed at set intervals."
msgstr ""
#: ../../admin/cron.rst:17
msgid "Most common examples of cron jobs in Elgg include:"
msgstr ""
#: ../../admin/cron.rst:19
msgid "sending out queued notifications"
msgstr ""
#: ../../admin/cron.rst:20
msgid "rotating the system log in the database"
msgstr ""
#: ../../admin/cron.rst:21
msgid "collecting garbage in the database (compacting the database by removing entries that are no longer required)"
msgstr ""
#: ../../admin/cron.rst:23
msgid "Plugins can add jobs by registering a plugin hook handler for one of the following cron intervals:"
msgstr ""
#: ../../admin/cron.rst:25
msgid "``minute`` - Run every minute"
msgstr ""
#: ../../admin/cron.rst:26
msgid "``fiveminute`` - Run every 5 minutes"
msgstr ""
#: ../../admin/cron.rst:27
msgid "``fifteenmin`` - Run every 15 minutes"
msgstr ""
#: ../../admin/cron.rst:28
msgid "``halfhour`` - Run every 30 minutes"
msgstr ""
#: ../../admin/cron.rst:29
msgid "``hourly`` - Run every hour"
msgstr ""
#: ../../admin/cron.rst:30
msgid "``daily`` - Run every day"
msgstr ""
#: ../../admin/cron.rst:31
msgid "``weekly`` - Run every week"
msgstr ""
#: ../../admin/cron.rst:32
msgid "``monthly`` - Run every month"
msgstr ""
#: ../../admin/cron.rst:33
msgid "``yearly`` - Run every year"
msgstr ""
#: ../../admin/cron.rst:50
msgid "How does it work?"
msgstr ""
#: ../../admin/cron.rst:52
msgid "``crontab`` must be setup in such a way as to activate Elgg cron handler every minute, or at a specific interval. Once cron tab activates the cron job, Elgg executes all hook handlers attached to that interval."
msgstr ""
#: ../../admin/cron.rst:55
msgid "If you have SSH access to your Linux servers, type ``crontab -e`` and add your crontab configuration."
msgstr ""
#: ../../admin/cron.rst:61
msgid "The above command will run every minute and activate all due cron jobs."
msgstr ""
#: ../../admin/cron.rst:63
msgid "Optionally you can activate handlers for a specific interval:"
msgstr ""
#: ../../admin/cron.rst:70
msgid "More information about cron can be found at:"
msgstr ""
#: ../../admin/duplicate-installation.rst:2
msgid "Duplicate Installation"
msgstr ""
#: ../../admin/duplicate-installation.rst:12
msgid "Why Duplicate an Elgg Installation?"
msgstr ""
#: ../../admin/duplicate-installation.rst:14
msgid "There are many reasons you may want to duplicate an Elgg installation: moving the site to another server, creating a test or development server, and creating functional backups are the most common. To create a successful duplicate of an Elgg site, 3 things need to be copied:"
msgstr ""
#: ../../admin/duplicate-installation.rst:17
msgid "Database"
msgstr ""
#: ../../admin/duplicate-installation.rst:18
msgid "Data from the data directory"
msgstr ""
#: ../../admin/duplicate-installation.rst:19
msgid "Code"
msgstr ""
#: ../../admin/duplicate-installation.rst:21
msgid "Also at least 5 pieces of information must be changed from the copied installation:"
msgstr ""
#: ../../admin/duplicate-installation.rst:23
msgid "``elgg-config/settings.php`` file which could also be in the pre 2.0 location ``engine/settings.php``"
msgstr ""
#: ../../admin/duplicate-installation.rst:24
msgid "``.htaccess`` file (Apache) or Nginx configuration depending on server used"
msgstr ""
#: ../../admin/duplicate-installation.rst:25
msgid "database entry for your site entity"
msgstr ""
#: ../../admin/duplicate-installation.rst:26
msgid "database entry for the installation path"
msgstr ""
#: ../../admin/duplicate-installation.rst:27
msgid "database entry for the data path"
msgstr ""
#: ../../admin/duplicate-installation.rst:30
msgid "What Is Not Covered in This Tutorial"
msgstr ""
#: ../../admin/duplicate-installation.rst:32
msgid "This tutorial expects a basic knowledge of Apache, MySQL, and Linux commands. As such, a few things will not be covered in this tutorial. These include:"
msgstr ""
#: ../../admin/duplicate-installation.rst:35
msgid "How to backup and restore MySQL databases"
msgstr ""
#: ../../admin/duplicate-installation.rst:36
msgid "How to configure Apache to work with Elgg"
msgstr ""
#: ../../admin/duplicate-installation.rst:37
msgid "How to transfer files to and from your production server"
msgstr ""
#: ../../admin/duplicate-installation.rst:40
msgid "Before You Start"
msgstr ""
#: ../../admin/duplicate-installation.rst:42
msgid "Before you start, make sure the Elgg installation you want to duplicate is fully functional. You will also need the following items:"
msgstr ""
#: ../../admin/duplicate-installation.rst:44
msgid "A backup of the live Elgg database"
msgstr ""
#: ../../admin/duplicate-installation.rst:45
msgid "A place to copy the live database"
msgstr ""
#: ../../admin/duplicate-installation.rst:47
msgid "A server suitable for installing duplicate Elgg site"
msgstr ""
#: ../../admin/duplicate-installation.rst:47
msgid "(This can be the same server as your production Elgg installation.)"
msgstr ""
#: ../../admin/duplicate-installation.rst:49
msgid "Backups of the database can be obtained various ways, including phpMyAdmin, the MySQL official GUI, and the command line. Talk to your host for information on how to backup and restore databases or use Google to find information on this."
msgstr ""
#: ../../admin/duplicate-installation.rst:52
msgid "During this tutorial, we will make these assumptions about the production Elgg site:"
msgstr ""
#: ../../admin/duplicate-installation.rst:54
msgid "The URL is ``http://www.myelgg.org/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:55
msgid "The installation path is ``/var/www/elgg/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:56
msgid "The data directory is ``/var/data/elgg/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:57
#: ../../admin/duplicate-installation.rst:68
msgid "The database host is ``localhost``"
msgstr ""
#: ../../admin/duplicate-installation.rst:58
msgid "The database name is ``production_elgg``"
msgstr ""
#: ../../admin/duplicate-installation.rst:59
#: ../../admin/duplicate-installation.rst:70
msgid "The database user is ``db_user``"
msgstr ""
#: ../../admin/duplicate-installation.rst:60
#: ../../admin/duplicate-installation.rst:71
msgid "The database password is ``db_password``"
msgstr ""
#: ../../admin/duplicate-installation.rst:61
#: ../../admin/duplicate-installation.rst:72
msgid "The database prefix is ``elgg``"
msgstr ""
#: ../../admin/duplicate-installation.rst:63
msgid "At the end of the tutorial, our test Elgg installation details will be:"
msgstr ""
#: ../../admin/duplicate-installation.rst:65
msgid "The URL is ``http://test.myelgg.org/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:66
msgid "The installation path is ``/var/www/elgg_test/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:67
msgid "The data directory is ``/var/data/elgg_test/``"
msgstr ""
#: ../../admin/duplicate-installation.rst:69
msgid "The database name is ``test_elgg``"
msgstr ""
#: ../../admin/duplicate-installation.rst:75
msgid "Copy Elgg Code to the Test Server"
msgstr ""
#: ../../admin/duplicate-installation.rst:77
msgid "The very first step is to duplicate the production Elgg code. In our example, this is as simple as copying ``/var/www/elgg/`` to ``/var/www/elgg_test/``."
msgstr ""
#: ../../admin/duplicate-installation.rst:85
msgid "Copy Data to the Test Server"
msgstr ""
#: ../../admin/duplicate-installation.rst:87
msgid "In this example, this is as simple as copying ``/var/data/elgg/`` to ``/var/data/elgg_test/``."
msgstr ""
#: ../../admin/duplicate-installation.rst:93
msgid "If you don't have shell access to your server and have to ftp the data, you may need to change ownership and permissions on the files."
msgstr ""
#: ../../admin/duplicate-installation.rst:97
msgid "You also need to delete cache directories from your disk. These correspond to ``cacheroot`` and ``assetroot`` directories in your config."
msgstr ""
#: ../../admin/duplicate-installation.rst:100
msgid "Edit settings.php"
msgstr ""
#: ../../admin/duplicate-installation.rst:102
msgid "The ``elgg-config/settings.php`` file contains the database configuration details. These need to be adjusted for your new test Elgg installation. In our example, we'll look in ``/var/www/elgg_test/elgg-config/settings.php`` and find the lines that look like this:"
msgstr ""
#: ../../admin/duplicate-installation.rst:127
msgid "We need to change these lines to match our new installation:"
msgstr ""
#: ../../admin/duplicate-installation.rst:155
msgid "Notice the ``$CONFIG->dbname`` has changed to reflect our new database."
msgstr ""
#: ../../admin/duplicate-installation.rst:158
msgid "Copy Elgg Database"
msgstr ""
#: ../../admin/duplicate-installation.rst:160
msgid "Now the database must be copied from ``elgg_production`` to ``elgg_test``. See your favorite MySQL manager's documentation for how to make a duplicate database. You will generally export the current database tables to a file, create the new database, and then import the tables that you previously exported."
msgstr ""
#: ../../admin/duplicate-installation.rst:164
msgid "You have two options on updating the values in the database. You could change the values in the export file or you could import the file and change the values with database queries. One advantage of modifying the dump file is that you can also change links that people have created to content within your site. For example, if people have bookmarked pages using the bookmark plugin, the bookmarks will point to the old site unless your update their URLs."
msgstr ""
#: ../../admin/duplicate-installation.rst:170
msgid "Database Entries"
msgstr ""
#: ../../admin/duplicate-installation.rst:172
msgid "We must now change 4 entries in the database. This is easily accomplished with 4 simple SQL commands:"
msgstr ""
#: ../../admin/duplicate-installation.rst:189
msgid "Check .htaccess"
msgstr ""
#: ../../admin/duplicate-installation.rst:191
msgid "If you have made changes to .htaccess that modify any paths, make sure you update them in the test installation."
msgstr ""
#: ../../admin/duplicate-installation.rst:194
msgid "Update Webserver Config"
msgstr ""
#: ../../admin/duplicate-installation.rst:196
msgid "For this example, you must edit the Apache config to enable a subdomain with a document root of ``/var/www/elgg_test/``. If you plan to install into a subdirectory of your document root, this step is unnecessary."
msgstr ""
#: ../../admin/duplicate-installation.rst:199
msgid "If you're using Nginx, you need to update server config to match new paths based on ``install/config/nginx.dist``."
msgstr ""
#: ../../admin/duplicate-installation.rst:202
msgid "Run upgrade.php"
msgstr ""
#: ../../admin/duplicate-installation.rst:204
msgid "To regenerate cached data, make sure to run ``http://test.myelgg.org/upgrade.php``"
msgstr ""
#: ../../admin/duplicate-installation.rst:207
msgid "Tips"
msgstr ""
#: ../../admin/duplicate-installation.rst:209
msgid "It is a good idea to keep a test server around to experiment with installing new mods and doing development work. If you automate restorations to the ``elgg_test`` database, changing the ``$CONFIG`` values and adding the follow lines to the end of the ``elgg_test/elgg-config/settings.php`` file will allow seamless re-writing of the MySQL database entries."
msgstr ""
#: ../../admin/duplicate-installation.rst:235
msgid ":doc:`backup-restore`"
msgstr ""
#: ../../admin/getting-help.rst:2
msgid "Getting Help"
msgstr ""
#: ../../admin/getting-help.rst:4
msgid "Having a problem with Elgg? The best way to get help is to ask at the `Community Site`_. This site is community supported by a large group of volunteers. Here are a few tips to help you get the help you need."
msgstr ""
#: ../../admin/getting-help.rst:13
msgid "Getting help"
msgstr ""
#: ../../admin/getting-help.rst:16
msgid "Don't be a `Help Vampire`_"
msgstr ""
#: ../../admin/getting-help.rst:18
msgid "We were all newbies at one time, but we can all learn. Not showing that you are making attempts to learn on your own or do your own research is off putting for those helping. Also, very generic questions like \"How do I build a forum?\" are almost impossible to answer."
msgstr ""
#: ../../admin/getting-help.rst:23
msgid "Search first"
msgstr ""
#: ../../admin/getting-help.rst:25
msgid "Be sure to search the documentation (this site), the `Community Site`_, and Google before asking a question. New users to Elgg frequently have the same questions, so please search. People are less inclined to reply to a post that has been answered many other times or that can be answered easily by Googling."
msgstr ""
#: ../../admin/getting-help.rst:28
msgid "Ask once"
msgstr ""
#: ../../admin/getting-help.rst:30
msgid "Posting the same questions in multiple places makes it hard to answer you. Ask your question in one place only. Duplicate questions may be moderated."
msgstr ""
#: ../../admin/getting-help.rst:33
msgid "Include Elgg Version"
msgstr ""
#: ../../admin/getting-help.rst:35
msgid "Different versions of Elgg have different features (and different bugs). Including the version of Elgg that you are using will help those helping you."
msgstr ""
#: ../../admin/getting-help.rst:38
msgid "Have a reasonable profile"
msgstr ""
#: ../../admin/getting-help.rst:40
msgid "Profiles that look like spam or have silly names will often be ignored. Joviality is fine, but people are more likely to help Michael than 1337elggHax0r."
msgstr ""
#: ../../admin/getting-help.rst:43
msgid "Post in the appropriate forum"
msgstr ""
#: ../../admin/getting-help.rst:45
msgid "Check to make sure you're posting in the right forum. If you have a question about creating a plugin, don't post to the Elgg Feedback forum. If you need help installing Elgg, post to Technical Support instead of the Theming group."
msgstr ""
#: ../../admin/getting-help.rst:48
msgid "Use a descriptive topic title"
msgstr ""
#: ../../admin/getting-help.rst:50
msgid "Good topic titles concisely describe your problem or question. Bad topic titles are vague, contain all capital letters, and excessive punctuation."
msgstr ""
#: ../../admin/getting-help.rst:52
msgid "Good title: \"White screen after upgrading to 1.7.4.\""
msgstr ""
#: ../../admin/getting-help.rst:54
msgid "Bad title: \"URGENT!!!!! site broke ;-( losing money help!!!!!!!!!!!\""
msgstr ""
#: ../../admin/getting-help.rst:57
msgid "Be detailed"
msgstr ""
#: ../../admin/getting-help.rst:59
msgid "Include as many details about your problem as possible. If you have a live site, include a link. Be forthcoming if community members might ask for more information. We can't help you if you won't give any details!"
msgstr ""
#: ../../admin/getting-help.rst:62
msgid "Keep it public"
msgstr ""
#: ../../admin/getting-help.rst:64
msgid "This is a public forum for the good of the Elgg project. Keep posts public. There's no reason for anyone to ask you to send a private message or email. Likewise, there's no reason to ask anyone to send a private email to you. Post in the public."
msgstr ""
#: ../../admin/getting-help.rst:67
msgid "Guidelines"
msgstr ""
#: ../../admin/getting-help.rst:69
msgid "In addition to the `site-wide Terms and Policies`_, following these guidelines keeps our community site useful and safe for everyone."
msgstr ""
#: ../../admin/getting-help.rst:74
msgid "Content"
msgstr ""