1. VW4
  2. Manual Mode Issues
 Printable Version

https://www.vaultwiki.org/pages/Book/Documentation/VW4:Manual-Mode-Issues

This page has been seen 437,487 times.

    • Created by
      on
Due to a bug in VaultWiki's progress system in versions prior to 4.0.14, using Manual Mode to perform the installation or upgrades may have resulted in incomplete installations or upgrades. What follows is a known list of possible side effects, depending on when Manual Mode was used.

Note:If running an unspecified upgrade script is suggested as a solution, make sure to use 4.0.14 or a later version.
Note:
  • This page only lists steps that were affected by default. If progress was manipulated manually by entering step numbers in the URL, it is possible that steps not listed below were affected.
  • Any issue that can be attributed to this issue will not be considered a new bug. Beginning with 4.0.14, which corrects the underlying cause, such issues will only be cleaned up on an individual basis via the methods described below or by private support tickets.

Installation

  1. The wiki has no languages. Solution: Visit Wiki Admin Panel > Languages > Language Manager to create one, and select a default language.
  2. There are no wiki settings. Solution: Manually run the install step:
    • Lite version under vBulletin: 14
    • Lite version under XenForo: 13
    • vBulletin: 16
    • XenForo: 15
  3. In XenForo, the wiki does not appear in the forum navigation bar, and manually navigating to the wiki shows a variation on a not-found error. Solution: After resolving #2, run the upgrade script.
  4. In XenForo, some features, including but not limited to profile counts and integrations, do not function. Solution: After resolving #2, run the upgrade script.
  5. In vBulletin 4.1.11 or later, the wiki has no mobile style. Solution: After resolving #2, run the upgrade script. (Note: The Lite version does not include a mobile style).
  6. In vBulletin 4.2 or later, the wiki does not appear in the forum navigation bar. Solution: After resolving #2, run the upgrade script.
  7. In vBulletin earlier than 4.2, the wiki never runs most deferred tasks (such as subscription mails, calculating view counts, cleaning up stale cache entries). Solution: After resolving #2, run the upgrade script.

Upgrades

Lite to Full

  1. In vBulletin, the admin notice about upgrading to the full version was not removed. Solution: MySQL query:
    Code:
    DELETE FROM adminmessage
    WHERE varname = 'vw_admin_upgrade_lite'
    LIMIT 1

  2. In XenForo, default entries were not added to the database. Visiting any wiki page may result in database errors. Solution: Private ticket support.
  3. The default attachment rules were not added. All attachments uploaded to the wiki receive an error about exceeding the maximum allowed file size. Solution: Private ticket support.

Any Upgrade

  1. In vBulletin, settings were not updated. Solution: Run the upgrade script.
  2. In XenForo, event listeners were not updated. Some wiki features may not function properly. Solution: Run the upgrade script.
  3. In vBulletin 4.1.11 or later, the wiki has no mobile style, or the mobile style was not updated. Solution: Run the upgrade script. (Note: The Lite version does not include a mobile style).
  4. In XenForo, template modifications were not updated. Some wiki features may not function properly. Solution: Run the upgrade script.
  5. In vBulletin 4.2 or later, the forum navigation bar was not updated, and may not contain wiki links. Solution: Run the upgrade script.
  6. In vBulletin earlier than 4.2, the wiki may not run new deferred tasks (such as subscription mails, calculating view counts, cleaning up stale cache entries). Solution: Run the upgrade script.
  7. In XenForo, the Upgrade Complete message may not appear.

4.0.0 Alpha 5 to 4.0.0 Alpha 6

  1. The number of characters changed between edits, as displayed on the History tab and other locations, may be incorrect for some edits that occurred before 4.0.0 Alpha 6.

4.0.0 Beta 3 to 4.0.0 Beta 4

  1. In vBulletin versions that had upgraded from VaultWiki 3, the table vw_report may have no PRIMARY KEY. Solution: MySQL query:
    Code:
    ALTER TABLE vw_report
    ADD PRIMARY KEY (reportid),
    DROP INDEX reportid

4.0.0 Beta 4 to 4.0.0 Beta 5

  1. User synonym and anonymous page counts may be incorrect. Solution: Go to Wiki Admin Panel > Maintenance > Rebuild Counters / Caches > User Contribution Counts, and choose each of Synonyms and Anonymous Pages.

4.0.0 Gamma 2 to 4.0.0 Gamma 3

  1. Incorrect area relationships were not corrected. Solution: Private ticket.

4.0.0 Gamma 5 to 4.0.0 Gamma 6

  1. In the full version under XenForo, several columns are missing from the vw_comment, vw_discussion, vw_redirect, and vw_revision tables, resulting in database errors. Solution: Private ticket.
  2. In the full version, some subscribed users may be unable to unsubscribe while subscriptions are disabled in settings (CAN-SPAM violation). Solution: Private ticket.

4.0.0 Gamma 6 to 4.0.0 Gamma 7

  1. The System area might be indexed by search engines. Solution: Go to Wiki Admin Panel > Structures > Area Manager, edit the System area, and update Miscellaneous Options > Search Engines Ignore This Area.

4.0.0 Gamma 7 to 4.0.0 RC 1

  1. The current versions of some pages that were affected by a bug may show content that has not been approved by a moderator. Solution: Private ticket.
  2. Some file updates may be incorrectly listed as rollbacks on the History tab. Solution: Private ticket.

4.0.0 RC 1 to 4.0.0 RC 2

  1. Subscriptions to pages that were deleted prior to RC 2 may be listed in subscription management meaninglessly (CAN-SPAM violation). Solution: Private ticket.
  2. Some attachments may still show that a file update is awaiting moderator review after it was already reviewed prior to RC 2. Solution: Private ticket.
  3. Some tasks that were deferred prior to RC 2 never complete. Solution: Private ticket.

4.0.0 RC 2 to 4.0.0 RC 3

  1. In the full version under vBulletin, the WIDGET BB-Code may be missing. Solution: Upgrade to 4.0.6 or later.
  2. In the full version under vBulletin > 3.7.x, some pages may still show an edit awaiting moderator review after it was already reviewed prior to RC 3. Solution: Private ticket.

4.0.0 RC 3 to 4.0.0 RC 4

  1. The column vw_revision.parentid is missing. This may cause database errors. Solution: MySQL query:
    Code:
    ALTER TABLE vw_revision
    ADD COLUMN parentid INT(11) UNSIGNED NOT NULL DEFAULT '0',
    ADD INDEX parentid (parentid)


4.0.0 RC 4 to 4.0.0 RC 5

  1. The default value for vw_route.sortkey was not set. Live-search results may be ordered incorrectly. Solution: Private ticket.
  2. Maximum word lengths were not set. Auto-links may not function correctly. Solution: Private ticket.
  3. In the Lite version, parent IDs for edits were not set. This may cause future features to function incorrectly. Solution: Private ticket.
  4. In the full version, user upload counts were not calculated. User upload counts may be incorrect. Solution: Go to Wiki Admin Panel > Maintenance > Rebuild Counters / Caches > User Contribution Counts, and choose File Uploads.
  5. In the full version, category content counts were not calculated. Counts of category contents may be incorrect. Solution: Upgrade to 4.0.12 or later.
  6. In the Lite version, default Block Permissions were not set for usergroups. Solution: In the Wiki Admin Panel, go to Content > Sidebar Blocks > Modify Permissions, and set usergroup permissions manually.
  7. In XenForo, the vw_report table was not removed. Solution: MySQL query:
    Code:
    DROP TABLE vw_report

4.0.0 RC 5 to 4.0.0

  1. In the full version, duplicate contents in categories were not removed. Solution: Private ticket.

4.0.0 to 4.0.1

  1. Default Block Permissions were not set for usergroups. Solution: In the Wiki Admin Panel, go to Content > Sidebar Blocks > Modify Permissions, and set usergroup permissions manually.
  2. In the full version, the order of book chapters was not calculated. Books may appear to be empty, have incorrect chapter order, or cause database errors. Solution: Private ticket.

4.0.1 to 4.0.2

  1. Permission for "Can view list of contents" and "Can remove contents from" was not mapped from existing permissions for Books, Categories, or Feeds. Solution: Manually update permissions.
  2. Feeds that were created but could not be found when opened were not fixed. Solution: Private ticket.

4.0.2 to 4.0.3

  1. In the full version, the column vw_lastupdate.updateid was not added. This may cause database errors. Solution: MySQL query:
    Code:
    ALTER TABLE vw_lastupdate
    DROP PRIMARY KEY,
    ADD INDEX node_lasttype (nodeid, nodetypeid, lasttypeid);
    ALTER TABLE vw_lastupdate
    ADD COLUMN updateid INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
    ADD PRIMARY KEY (updateid);

4.0.3 to 4.0.4

  1. Block-types were not updated to the new format. Sidebar blocks may not function correctly. Solution: Private ticket.
  2. In the full version, some pages may still show an edit awaiting moderator review after it was already reviewed prior to 4.0.4. Solution: Private ticket.
  3. In the full version, duplicate moderation queue items were not removed. Solution: Address the queue items manually.
  4. In the Lite version, existing page counters were not moved. Pages may show incorrect content counts. Solution: Upgrade to 4.0.14 or later.
  5. In the full version, the indexes on vw_counter.routeid and vw_lastupdate.routeid were not added. This may cause database errors. Solution: Private ticket.
  6. In the Lite version, counter records were not added for existing pages. Pages may show incorrect content counts. Solution: Upgrade to 4.0.14 or later.
  7. In the full version, the CHAR BB-Code was not added. Under XenForo, the WIDGET BB-Code was not added. Solution: Upgrade to 4.0.6 or later.
  8. In the Lite version under XenForo, existing news feed entries were not updated to the new format. Some news feed entries shown may be incorrect. Solution: Private ticket.

4.0.5 to 4.0.6

  1. In the full version, the column vw_prefix.bbcode_varname was not added. This would have prevented the upgrade from progressing any further. If the following step was skipped manually, this may result in database errors. Solution: MySQL query:
    Code:
    ALTER TABLE vw_prefix
    ADD COLUMN bbcode_varname VARCHAR(32) NOT NULL DEFAULT ''

  2. In the full version, attachment-based icons for feeds were not converted to the new format. Those icons would not work correctly. Solution: Private ticket.
  3. In the Lite version under vBulletin, the columns bbcode.vw_varname, bbcode.vw_options, and bbcode.productid were not added. This may have prevented the upgrade from progressing further. Solution: MySQL query:
    Code:
    ALTER TABLE bbcode
    ADD COLUMN vw_varname VARCHAR(32) NOT NULL DEFAULT '',
    ADD COLUMN vw_options INT(4) UNSIGNED NOT NULL DEFAULT '0',
    ADD COLUMN productid VARCHAR(15) NOT NULL DEFAULT '',
    ADD INDEX vw_varname (vw_varname),
    ADD INDEX productid (productid)

  4. In the Lite version under XenForo, the columns vw_bbcode.varname and vw_bbcode.productid were not added. This may have prevented the upgrade from progressing further. Solution: MySQL query:
    Code:
    ALTER TABLE vw_bbcode
    ADD COLUMN varname VARCHAR(32) NOT NULL DEFAULT '',
    ADD COLUMN productid VARCHAR(25) NOT NULL DEFAULT '',
    ADD INDEX productid (productid)

  5. In the full version under XenForo, the vw_tagged table was not removed. Solution: MySQL query:
    Code:
    DROP TABLE vw_tagged

  6. In the full version under vBulletin 4, stale content tags were not removed. Solution: MySQL query:
    Code:
    DELETE FROM tagcount WHERE contenttypeid = 9999

4.0.6 to 4.0.7

  1. In the full version, duplicate records in vw_counter due to a previous failed step were not removed. The next step intended to re-execute that failed step may also fail. Solution: Private ticket.

4.0.7 to 4.0.8

  1. In the full version, corrupt categories were not restored or removed. Solution: Private ticket.
  2. In the full version, deleted content was not removed from some feeds. Solution: Private ticket.
  3. Last update entries of moved content were not removed. This may cause the last update field for some content to be incorrect. Solution: Private ticket.

4.0.8 to 4.0.9

  1. Permission to post videos in wiki comments was not mapped from other comment permissions. Solution: Manually adjust permissions.

4.0.9 to 4.0.10

  1. In the full version, the table vw_team_member was not created. This may cause database errors. Solution: MySQL query:
    Code:
    CREATE TABLE vw_team_member
    (
    	teammemberid INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
    	teamid INT(11) UNSIGNED NOT NULL DEFAULT '0',
    	userid INT(11) UNSIGNED NOT NULL DEFAULT '0',
    	dateline INT(11) UNSIGNED NOT NULL DEFAULT '0',
    	`type` VARCHAR(15) NOT NULL DEFAULT '',
    	PRIMARY KEY (teammemberid),
    	INDEX teamid (teamid),
    	INDEX userid (userid),
    	INDEX membertype (teamid, `type`)
    )

  2. In XenForo, wiki integration with XenForo statistics was not added. Solution: Private ticket.
  3. In vBulletin, missing wiki super-moderators were not added. Solution: Add wiki moderators manually.

4.0.10 to 4.0.11

  1. In the full version, searchable metadata for existing pages was not set. Solution: Private ticket.
  2. In the Lite version, content counts for feeds were not recalculated. Some feed content counts may be incorrect. Solution: Upgrade to 4.0.14 or higher.
  3. In the full version under vBulletin, massive wiki attachment disk space allotments were not reduced. Solution: Upgrade to 4.0.14 or higher.

4.0.12 to 4.0.13

  1. The last update cache was not cleared. The last update field for some content may be incorrect. Solution: MySQL query:
    Code:
    TRUNCATE TABLE vw_lastupdatecache