a:99:{s:17:"FU_UPGRADER_TITLE";s:16:"Composr upgrader";s:17:"FU_UPGRADER_INTRO";s:159:"This is the Composr upgrade tool. This tool is a part of Composr, but it is intentionally kept lightweight to keep it working even if Composr is partly broken.";s:13:"FU_LOGIN_INFO";s:131:"Once you log in you will be presented with some options to help you upgrade or perform maintenance on your Composr-powered website.";s:25:"FU_LOGIN_INFO_PASS_FORGET";s:332:"If so, find the <kbd>master_password</kbd> line of your <kbd>_config.php</kbd> file and put in a new temporary password (the one written there won't work because it is encrypted). Once you have done this you should promptly use the <kbd>config_editor.php</kbd> script to change the password, as this will save it again as encrypted.";s:26:"FU_LOGIN_FORGOT_PASSWORD_Q";s:21:"Forgot your password?";s:10:"FU_CHOICES";s:43:"The following choices are available to you:";s:21:"WARNING_FILE_OUTDATED";s:647:"<p>The following files may have been superseded by new versions, but you have overrides/customisations blocking the newest versions. Look into this and consider reincorporating your changes into our new version. If this is not done, bugs (potentially security holes) may occur, or be left unfixed. If you edited using an inbuilt editor, the file on which you based it will be saved as <kbd>file.editfrom</kbd>: you may use a tool such as <a href="http://winmerge.sourceforge.net/" target="_blank">WinMerge</a> to compare the <kbd>editfrom</kbd> file to your own, and then apply those same changes to the latest version of the file.</p><ul>{1}</ul>";s:18:"WARNING_FILE_ALIEN";s:410:"<p>The following alien files were found in Composr and possibly should be deleted. It may be that these files are remnants of the previous version or files from uninstalled addons (these ones are pre-ticked/checked), and they may cause problems if left behind. Please check each file to see what it is, and if you believe it to be an outdated file, delete it. Please take a backup first though!</p><ul>{1}</ul>";s:18:"WARNING_FILE_ADDON";s:394:"<p>The following files relating to non-bundled addons were found in Composr and probably should be deleted if you have done a major upgrade. They may not be compatible with the version you are currently running. If you delete the files you will be able to restore them by importing the latest version of the addons involved (Composr will help you with this from the Admin Zone).</p><ul>{1}</ul>";s:10:"FILE_MOVED";s:147:"A module file, <kbd>{1}</kbd>, was apparently moved from the &ldquo;<kbd>{2}</kbd>&rdquo; zone to the &ldquo;<kbd>{3}</kbd>&rdquo; zone previously.";s:15:"NO_UPGRADE_DONE";s:45:"<p>No specific upgrade needed to be done.</p>";s:11:"AUTO_MERGED";s:127:"[don't worry this has just been automatically merged using the <kbd>.editfrom</kbd> file, and a revision backup has been taken]";s:18:"FU_UPGRADED_MODULE";s:30:"Upgraded module <kbd>{1}</kbd>";s:19:"FU_INSTALLED_MODULE";s:31:"Installed module <kbd>{1}</kbd>";s:17:"FU_UPGRADED_BLOCK";s:29:"Upgraded block <kbd>{1}</kbd>";s:18:"FU_INSTALLED_BLOCK";s:30:"Installed block <kbd>{1}</kbd>";s:17:"FU_UPGRADED_ADDON";s:23:"Upgraded <kbd>{1}</kbd>";s:18:"FU_INSTALLED_ADDON";s:24:"Installed <kbd>{1}</kbd>";s:14:"FU_NEEDS_CHMOD";s:47:"File not writable but should be: <kbd>{1}</kbd>";s:16:"FU_NEEDS_UNCHMOD";s:75:"File <strong>is</strong> writable but perhaps should not be: <kbd>{1}</kbd>";s:23:"FU_UPGRADED_CORE_TABLES";s:28:"<p>Upgraded core tables.</p>";s:20:"FU_ALL_CHMODDED_GOOD";s:35:"<p>All permissions are correct.</p>";s:18:"WARNING_FILE_CHMOD";s:66:"<p>The following files have incorrect permissions:</p><ul>{1}</ul>";s:21:"WARNING_MOVED_MODULES";s:321:"<p>The upgrader has detected that some Composr modules were probably previously moved. However because the new Composr files have been uploaded, the new Composr module files are back where they used to be. You therefore need to do the moving again, overwriting the old versions that were previously moved.</p><ul>{1}</ul>";s:18:"FU_UPGRADE_MODULES";s:38:"<p>Upgraded/installed:</p><ul>{1}</ul>";s:17:"FU_NO_CNS_UPGRADE";s:44:"<p>Conversr did not need to be upgraded.</p>";s:14:"FU_UPGRADE_CNS";s:16:"Upgrade Conversr";s:19:"FU_MUST_UPGRADE_CNS";s:28:"<div>Now you must {1}.</div>";s:11:"FU_FTP_INFO";s:303:"<p>If you need to do a file extraction or permission-fixing, then you'll probably need to enter <abbr title="File Transfer Protocol">FTP</abbr> details below. If you don't need to do these, then blank out the fields (otherwise the upgrader will try to connect and fail if the details are incorrect).</p>";s:12:"FU_UP_INFO_1";s:156:"The on-disk version of Composr is <strong>{1}</strong> and the in-database version is <strong>{2}</strong>. This means the database is currently up-to-date.";s:12:"FU_CLOSENESS";s:65:"<span>(The website is currently </span><em>{1}</em><span>)</span>";s:12:"FU_UP_INFO_2";s:165:"The on-disk version of Composr is <strong>{1}</strong> and the in-database version is <strong>{2}</strong>. This means a database upgrade has not yet been completed.";s:22:"FU_CLOSED_FOR_UPGRADES";s:95:"{1} will be closed for a brief time while upgrades are performed. We expect to be back shortly.";s:14:"FU_MAINTENANCE";s:11:"Maintenance";s:12:"FU_UPGRADING";s:9:"Upgrading";s:15:"FU_CLEAR_CACHES";s:12:"Clear caches";s:14:"FU_TAKE_BACKUP";s:173:"<strong>Take</strong> and <strong>test</strong> a backup, using whatever backup tools you are used to (integrated webhosting-control-panel tools recommended where available)";s:20:"FU_CHECK_PERMISSIONS";s:53:"Check missing/excess permissions, but do not fix them";s:18:"FU_FIX_PERMISSIONS";s:33:"Check and fix missing permissions";s:13:"FU_CLOSE_SITE";s:14:"Close the site";s:11:"FU_DOWNLOAD";s:33:"Transfer across new/updated files";s:17:"FU_INTEGRITY_SCAN";s:58:"Do a file integrity scan, *with* automatic theme upgrading";s:30:"FU_INTEGRITY_SCAN_NO_CSS_MERGE";s:24:"Do a file integrity scan";s:16:"FU_THEME_UPGRADE";s:32:"Upgrade themes (runs test first)";s:15:"FU_THEME_ERRORS";s:227:"Errors (&#x2717;) shown above won't stop the upgrade from happening, but may be indicative of a need for manual intervention after the upgrade is finished. Please keep a copy of them (put them into a document for safe keeping).";s:22:"FU_THEME_UPGRADE_FINAL";s:27:"Go ahead and upgrade themes";s:13:"FU_WILL_MERGE";s:294:"This will attempt to merge in default theme changes to your custom theme CSS. This is not perfect, it will likely result in some small theme errors that you would need to fix manually. Unless the upgrade specifies major theme changes, this step is not necessary. Are you sure you want to do it?";s:19:"FU_DATABASE_UPGRADE";s:68:"Do a database upgrade (upgrade/install core-database/modules/blocks)";s:16:"FU_NOT_FOR_PATCH";s:49:"<em>(Only needed for feature/major upgrades)</em>";s:11:"FU_TUTORIAL";s:40:"Carefully (re)read the upgrader tutorial";s:12:"FU_OPEN_SITE";s:13:"Open the site";s:7:"FU_BUGS";s:237:"The developers cannot make any guarantees about the speed of which any new bugs might be patched. It is your own responsibility to make and test a full website backup (files and database) before you upgrade, for if you need to roll-back.";s:16:"FU_RELEASE_NOTES";s:13:"Release notes";s:22:"FU_REFER_RELEASE_NOTES";s:80:"Read the release notes in the announcement for the version you are upgrading to.";s:16:"FU_UPGRADE_STEPS";s:13:"Upgrade steps";s:17:"FU_ESTIMATED_TIME";s:14:"Estimated time";s:13:"FU_FTP_NEEDED";s:122:"We could not perform filesystem operations without FTP details. Please go back and ensure you put in accurate FTP details.";s:7:"FU_STEP";s:4:"Step";s:17:"FU_CUSTOMISATIONS";s:214:"If you are doing a feature/major upgrade and have done a lot of themeing or have a lot of unofficial code it could potentially take up to days, as you would need to update a lot of code due to compatibility breaks.";s:20:"FU_FILE_UPGRADE_INFO";s:520:"<p>Whenever the developers make a new version of Composr, news is posted on <a target="_blank" title="compo.sr (this link will open in a new window)" href="http://compo.sr/site/news.htm">compo.sr</a>. Your Admin Zone will inform you and link direct to that news post. The news post will contain the URL to an upgrade file that you may use to update your site &ndash; feed that URL in here and the Composr upgrader will automatically extract it to the server, skipping files from official addons that you uninstalled.</p>";s:27:"FU_FILE_UPGRADE_INFO_MANUAL";s:553:"<p><strong>Important:</strong> This extraction step can be a bit precarious for large upgrades. If it does not finish correctly you can <a href="{1}" onclick="document.getElementById('wget').style.display='block';">generate a personalised manual upgrader</a> of the latest version which you can extract yourself.</p><p id="wget" style="display: none; word-wrap: break-word;">You can extract to your server using commands roughly as follows:<br /><kbd>cd /var/www/html<br />wget -O upgrade.tar "{1}"<br />tar xvf upgrade.tar<br />rm upgrade.tar</kbd></p>";s:10:"FU_DRY_RUN";s:57:"Do dry-run (show messages but don't actually do anything)";s:16:"FU_DOING_DRY_RUN";s:103:"Doing dry-run. The messages below reflect what would happen, but no destructive operations will be run.";s:12:"FU_CHECK_ALL";s:8:"Tick all";s:14:"FU_AUTO_HANDLE";s:63:"Automatically handle those ticked &ndash; delete/move as needed";s:15:"NO_ISSUES_FOUND";s:15:"No issues found";s:43:"WARNING_FILE_OUTDATED_ORIGINAL_AND_OVERRIDE";s:300:"<p>The following non-overridden files are outdated, as are the corresponding overridden files (you can find the correct versions for the original in the manual installer ZIP for the version you're running, but the overrides may still cause problems and might need removing/replacing):</p><ul>{1}</ul>";s:46:"WARNING_FILE_MISSING_ORIGINAL_BUT_HAS_OVERRIDE";s:174:"<p>The following original files to these overridden files are actually missing (you can find them in the manual installer ZIP for the version you're running):</p><ul>{1}</ul>";s:35:"WARNING_FILE_FROM_UNINSTALLED_ADDON";s:141:"<p>The following files are overridden, but the addons for them are uninstalled. You might need to remove your overrides also.</p><ul>{1}</ul>";s:34:"WARNING_FILE_MISSING_FILE_ENTIRELY";s:150:"<p>These files are actually missing and need uploading (you can find them in the manual installer ZIP for the version you're running):</p><ul>{1}</ul>";s:30:"WARNING_FILE_OUTDATED_ORIGINAL";s:139:"<p>These files are outdated (you can find the correct versions in the manual installer ZIP for the version you're running):</p><ul>{1}</ul>";s:25:"WARNING_FILE_FUTURE_FILES";s:153:"<p>These files do not match the ones bundled with your version, but claim to be newer (so these might be bug fixes someone has put here):</p><ul>{1}</ul>";s:18:"EXTRACTING_MESSAGE";s:274:"<strong>Extracting files</strong>. Please note that if execution halts without message during file extraction then the operation has not completed due to a timeout. If this happens (it can do on a small proportion of servers) try refreshing a few times to see if this works.";s:18:"U_SKIPPING_MESSAGE";s:50:"Skipping file (already up-to-date): <kbd>{1}</kbd>";s:20:"U_EXTRACTING_MESSAGE";s:31:"Extracting file: <kbd>{1}</kbd>";s:23:"U_RENAMED_ADDON_MESSAGE";s:127:"Addon <kbd>{1}</kbd> renamed to <kbd>{2}</kbd>. You should run the file integrity scan after upgrading to remove the old addon.";s:21:"U_NEW_ADDON_EXTRACTED";s:154:"Extracting new bundled addon for installation: <kbd>{1}</kbd>. You can uninstall this addon from the Addons Management page after upgrading if you desire.";s:17:"U_PACKING_MESSAGE";s:92:"Packing file into addon archive (for presence upon potential reinstallation): <kbd>{1}</kbd>";s:19:"FU_ERROR_CORRECTION";s:90:"Error correction (useful tools if doing a feature or major upgrade and encounter problems)";s:12:"FU_SAFE_MODE";s:103:"Launch site in safe mode [i.e. disable custom files] (requires you to be logged in as an administrator)";s:19:"FU_ADDON_MANAGEMENT";s:88:"Manage addons (you have {1} {1|addon|addons} that may need replacing/disabling/removing)";s:20:"FU_EXTRACTING_WINDOW";s:395:"We have done the low-risk updating, and now we need to proceed with the full extraction of {1} new/updated files. It will be performed in the frame below that will work through the files in steps.<br /><strong>Wait until all files are checked and it says &quot;Done!&quot; beneath them</strong>. If the extraction doesn't progress, check to see if you have any browser addons blocking refreshes.";s:25:"NO_DEFINED_THEME_UPGRADER";s:74:"There is no theme upgrader available for the version you are upgrading to.";s:23:"NON_RECOGNISED_CSS_FILE";s:159:"Could not recognise the <abbr title="Cascading Style Sheets">CSS</abbr> file <kbd>{1}</kbd> as being from version {2}, although we'll try and process it anyway";s:30:"CSS_RULE_UNMATCHED_css_replace";s:217:"Could not find a match for the <abbr title="Cascading Style Sheets">CSS</abbr> replacement rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{1}</kbd><br />&rarr;<br /><kbd style="white-space: pre">{2}</kbd>";s:30:"CSS_RULE_UNMATCHED_css_prepend";s:231:"Could not find a match for the <abbr title="Cascading Style Sheets">CSS</abbr> prepend rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{2}</kbd><br /><em>inserted before</em><br /><kbd style="white-space: pre">{1}</kbd>";s:29:"CSS_RULE_UNMATCHED_css_append";s:229:"Could not find a match for the <abbr title="Cascading Style Sheets">CSS</abbr> append rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{2}</kbd><br /><em>inserted after</em><br /><kbd style="white-space: pre">{1}</kbd>";s:32:"CSS_RULE_OVERMATCHED_css_replace";s:224:"Too many matches for the single-match <abbr title="Cascading Style Sheets">CSS</abbr> replacement rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{1}</kbd><br />&rarr;<br /><kbd style="white-space: pre">{2}</kbd>";s:32:"CSS_RULE_OVERMATCHED_css_prepend";s:238:"Too many matches for the single-match <abbr title="Cascading Style Sheets">CSS</abbr> prepend rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{2}</kbd><br /><em>inserted before</em><br /><kbd style="white-space: pre">{1}</kbd>";s:31:"CSS_RULE_OVERMATCHED_css_append";s:236:"Too many matches for the single-match <abbr title="Cascading Style Sheets">CSS</abbr> append rule for <kbd>{3}</kbd>:<br /><kbd style="white-space: pre">{2}</kbd><br /><em>inserted after</em><br /><kbd style="white-space: pre">{1}</kbd>";s:17:"CSS_FILE_UPGRADED";s:66:"Upgraded <abbr title="Cascading Style Sheets">CSS</abbr> file, {1}";s:19:"THEME_IMAGE_RENAMED";s:52:"Renamed theme image <kbd>{1}</kbd> to <kbd>{2}</kbd>";s:15:"THEME_IMAGE_NEW";s:70:"Copied in new theme image <kbd>{1}</kbd> and applied Theme Wizard seed";s:16:"TEMPLATE_RENAMED";s:40:"Renamed <kbd>{1}</kbd> to <kbd>{2}</kbd>";s:16:"TEMPLATE_ALTERED";s:33:"Made change within <kbd>{1}</kbd>";s:28:"TEMPLATE_WILL_NEED_RESTORING";s:133:"The template <kbd>{1}</kbd> is no longer valid due to major changes; you'll need to edit it again, using the latest version as a base";s:10:"SH_COMMAND";s:249:"<p>Here is a sh/bash/mingw command to run on your computer to assist you in isolating out the files to easily batch upload (you need to substitute in <kbd>manual-extracted-at-dir</kbd> and <kbd>temp-dir-to-upload-from</kbd>):<br /><kbd>{1}</kbd></p>";s:7:"RM_HINT";s:252:"<p>To delete in Commandr type the following commands separately in sequence:<br /><kbd>cd /raw<br />rm &lt;files-you-decided-to-delete&gt;</kbd><br />(you can copy and paste multi-line file lists onto the end of an Commandr command with no problem)</p>";s:21:"FU_REMOVE_ADDON_FILES";s:40:"Remove addon files (for developers only)";}