• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Bug
    • Error (Importing from VW 3.0.20 PL1 to VW 4.0.4)

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Error (Importing from VW 3.0.20 PL1 to VW 4.0.4)

    • Issue Tools
      • View Changes
    1. issueid=4320 June 5, 2015 7:26 AM
      Kirauni Kirauni is offline
      Junior Member
      Error (Importing from VW 3.0.20 PL1 to VW 4.0.4)
      The importer stops at step 13 (Importing wiki pages) with an SQL-Error (MAX_JOIN_SIZE)

      Hello,

      I've finally found some time to upgrade my VaultWiki 3.0.20 PL1 to VaultWiki 4.0.4. I've followed all the steps mentioned in the blog. Thank you very much for this great guide! However, I finally ran out of luck...
      When I clicked on "Import/Export" and picked "Vault Wiki 3" I got an error at step 13 ("Importing wiki pages").

      This is the SQL-Error message I got:
      Code:
      [...]
      Invalid SQL:
      SELECT `t`.`threadid` AS `threadid`,`t`.`title` AS `title`,`t`.`forumid` AS `forumid`,`t`.`visible` AS `visible`,`t`.`dateline` AS `dateline`,`p`.`postid` AS `postid`,`p`.`pagetext` AS `post_pagetext`,`p`.`userid` AS `userid`,`p`.`username` AS `username`,`p`.`attach` AS `attach`,`p`.`ipaddress` AS `ipaddress`,`p2`.`options` AS `protect`,`t`.`prefixid` AS `prefixid`,`a`.`groupid` AS `groupid`,`a`.`languageid` AS `languageid` FROM `vb_thread` `t`  LEFT JOIN `vb_vault_article` `a` ON (`t`.`threadid` = `a`.`threadid`) 
       LEFT JOIN `vb_post` `p` ON (`t`.`threadid` = `p`.`threadid` AND `p`.`parentid` = 0) 
       LEFT JOIN `vb_vault_protect` `p2` ON (`t`.`threadid` = `p2`.`targetid`)   WHERE  `t`.`forumid` IN (818,819,820,822,823,827)  ORDER BY `t`.`threadid` ASC  LIMIT 0,100;
      
      MySQL-Fehler  : The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
      Fehler-Nr.    : 1104
      Fehler-Zeit   : Friday, 05.06.2015 @ 13:01:27
      Datum         : Friday, 05.06.2015 @ 13:01:27
      Skript        : xxx/backup/admin_cp/wiki_cp.php?panel=impex&do=import&step=13&nostyle=1
      Referrer      : xxx/backup/admin_cp/wiki_cp.php?panel=impex&do=import&step=12&nostyle=1
      IP-Adresse    : xxx
      Benutzername  : xxxxx
      Klassenname   : vB_Database
      MySQL-Version : 5.5.42-37.1-log
      Now that "Max-Join-Size" issue strikes me as oddly familiar... I recall having similiar issue, when I updated from vBulletin 4.2.0 to 4.2.2 about 2 years ago. Back then, the support told me that I should increase the value of the MAX_JOIN_SIZE and so I called my hoster and asked them about it. They told me that the value already is around 200 millions, so that wasn't causing the problems. The support over at vBulletin couldn't help me either and so I tried to find a work around on my own. I finally found out that my styles were causing the errors. Once I had reduced the number of styles, the upgrade completed successfully.
      But now it has happend again during the import script for VaultWiki and I wonder if there's anything I can do about it. I don't think it is related to the number of styles this time, but I'm afraid that the number of forums and threads is causing this. Could that be the case? I have 3 Wikis in three forums on my board, but they don't have that many threads. And of course there's the images-forum, the categories and the books..., but that's pretty much about it. What I do have are several other forums, threads and posts apart from the wiki, because my site is quite old.

      Could you please help me to find a solution for this issue, because I really want to update my version of VW3, since some users are not able to view the wiki properly. (There's an "infinite loop error" when viewing a wiki page for one user, but it works fine for all the others..). Finally, the time has come to try out something new now and I'd be glad to hear from you, Pegasus.

      Thanks!

      ~Kirauni



      PS: Maybe there's a work around if I added
      Code:
      $vbulletin->db->query_write("
          SET SQL_BIG_SELECTS=1"
      );
      somwhere? But I don't know where to put it. Any ideas?
    Issue Details
    Issue Number 4320
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Importing
    Status Fixed
    Priority 2 - Fatal / Database Errors
    Affected Version 4.0.4
    Fixed Version 4.0.5
    Milestone (none)
    Software DependencyvBulletin 4.x
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags database, error, Import, sql, upgrade


    Page 1 of 2 12 Next LastLast


    1. June 5, 2015 10:03 AM
      pegasus pegasus is offline
      VaultWiki Team
      A query with the thread table joining on the post table (either first or second) would AT MOST need to examine total threads X total posts rows. In your case this is about 3,000,000,000 possibilities ---

      However, if you are using MySQL 5, then the optimizer should only be using threads found by the WHERE clause x total posts. This is more like 200,000,000 possibilities.

      More, I don't think MySQL would even try to examine that many rows if the database has proper indexes. That's kind of the point of indexing things, so that you don't have to examine every row. So it seems like your database might be missing some indexes.

      I would be happy to take a closer look if you would fill out a service request here: https://www.vaultwiki.org/members/?d...e&productid=20

      Please note that the largest wiki I know of that uses VaultWiki contains over 100k articles and they have not reported any issue like this when they imported or in regular use.
      Reply Reply
    2. June 5, 2015 12:12 PM
      Kirauni Kirauni is offline
      Junior Member
      Thank you very much for replying so quickly, Pegasus!

      I've filled out all the fields and you should be able to have a look at my testing site. I'm really glad for your help

      You're probably right that there's something wrong with my indexes, and I don't know why the number of forums and posts should be a problem. But that's what the error code implied. I didn't know that there could be something wrong with my database or its indexes. Perhaps you could tell me how to check that? That would be great!

      Again many thanks!
      Reply Reply
    3. June 7, 2015 11:11 AM
      pegasus pegasus is offline
      VaultWiki Team
      I made some changes to the importer, so it was able to finish successfully. In general these changes improve performance of some import commands and prevent errors by not trusting reported capabilities of the source database. I've published these changes as 4.0.4 build 006, so that you can run a live import before the next release if you want to.
      Reply Reply
    4. June 7, 2015 12:19 PM
      Kirauni Kirauni is offline
      Junior Member
      Thank you very much for looking into this matter and providing a changed importer. I'll set up another test-board and try it out as soon as possible.

      There's one more thing... Could you please tell me what exactly was causing these huge queries? Is there really something wrong with my database? If yes, I'd love to do something about it because things like these are bound to happen again sooner or later. Which reminds me... when I first ran the installation of vw4 on my testboard a few days ago, I got a similiar error message. I managed to fix this by deleting two styles and then the skript worked, but I guess that shouldn't happen. So I'm posting the code here to let you know. Sorry for not bringing it up earlier... I got so stuck at the other error that I completely forgot about the other issue.

      Invalid SQL:

      SELECT t1.templateid AS templateid_1, t1.title ,
      t2.templateid AS templateid_2, t2.title AS title2, t2.styleid AS styleid_2 ,
      t3.templateid AS templateid_3, t3.title AS title3, t3.styleid AS styleid_3 ,
      t4.templateid AS templateid_4, t4.title AS title4, t4.styleid AS styleid_4 ,
      t5.templateid AS templateid_5, t5.title AS title5, t5.styleid AS styleid_5
      FROM vb_template AS t1
      LEFT JOIN vb_template AS t2 ON (t1.title=t2.title AND t2.styleid=2)
      LEFT JOIN vb_template AS t3 ON (t1.title=t3.title AND t3.styleid=3)
      LEFT JOIN vb_template AS t4 ON (t1.title=t4.title AND t4.styleid=5)
      LEFT JOIN vb_template AS t5 ON (t1.title=t5.title AND t5.styleid=4)
      WHERE t1.styleid IN (-1,0)
      ORDER BY t1.title;

      MySQL-Fehler : The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
      Fehler-Nr. : 1104
      Fehler-Zeit : Friday, 05.06.2015 @ 11:04:00
      Datum : Friday, 05.06.2015 @ 11:04:01
      Skript : xxx/pride-backup/vault/install/index.php?step=18&nostyle=1&startat=31
      Referrer : xxx/pride-backup/vault/install/index.php?step=18&nostyle=1
      IP-Adresse : xxxxxxx
      Benutzername : Kirauni
      Klassenname : vB_Database
      MySQL-Version : 5.5.42-37.1-log
      Thanks again and I'll let you how things go
      Reply Reply
    5. June 7, 2015 1:26 PM
      pegasus pegasus is offline
      VaultWiki Team
      It looks like that template query (which should run whenever you upgrade vBulletin also) might not be hitting the index on title,styleid,templatetype. However, I don't really know why. Usually title,styleid should be enough for the optimizer to choose that index. I don't know off-hand what context this query is used in, to know if it's safe to modify with a templatetype condition, how you would patch it like that, or even if it would have an effect.

      If the query does not use an index, then it will have a join size of roughly
      NUMBER_OF_TEMPLATES^(NUMBER_OF_STYLES)
      Reply Reply
    6. June 8, 2015 11:55 AM
      Kirauni Kirauni is offline
      Junior Member
      Hmm... okay this sounds rather complicated. Just one quick questions: Where can I download 4.0.4 build 006? I didn't find it in the member's section unfortunately.


      EDIT: Nevermind... I found it. I didn't know it was included in the latest download of 4.0.4
      Reply Reply
    7. June 9, 2015 1:22 PM
      Kirauni Kirauni is offline
      Junior Member
      Okay, so the import within my first testing area worked fine. Now I've set up another one and the installation went pretty well (I removed some styles before, so that the other error wouldn't occur. I still have no idea how there could be something wrong with the indexes though...).

      I set the board to "debug mode" for additional information.
      Then I ran the import skript and at Step 22 (Importing Page view Counts) it suddenly said:

      Code:
      [...]
      Invalid SQL:
      UPDATE  `vb_vw_counter` SET `views` =  CASE `pageid` 
      		 WHEN 12 THEN 12 
      		 WHEN 19 THEN 19 
      		 WHEN 20 THEN 20 
      		 WHEN 21 THEN 21 
      		 WHEN 24 THEN 24 
      		 WHEN 34 THEN 34 
      		 WHEN 36 THEN 36 
      		 WHEN 37 THEN 37 
      		 WHEN 39 THEN 39 
      		 WHEN 40 THEN 40 
      		 WHEN 45 THEN 45 
      		 WHEN 47 THEN 47 
      		 WHEN 48 THEN 48 
      		 WHEN 49 THEN 49 
      		 WHEN 50 THEN 50 
      		 WHEN 51 THEN 51 
      		 WHEN 53 THEN 53 
      		 WHEN 56 THEN 56 
      		 WHEN 59 THEN 59 
      		 WHEN 60 THEN 60 
      		 WHEN 74 THEN 74 
      		 WHEN 76 THEN 76 
      		 WHEN 78 THEN 78 
      		 WHEN 80 THEN 80 
      		 WHEN 84 THEN 84 
      		 WHEN 85 THEN 85 
      		 WHEN 88 THEN 88 
      		 WHEN 92 THEN 92 
      		 WHEN 94 THEN 94 
      		 WHEN 95 THEN 95 
      		 WHEN 100 THEN 100 
      		 WHEN 101 THEN 101 
      		 WHEN 102 THEN 102 
      		 WHEN 103 THEN 103 
      		 WHEN 104 THEN 104 
      		 WHEN 107 THEN 107 
      		 WHEN 108 THEN 108 
      		 WHEN 109 THEN 109 
      		 WHEN 110 THEN 110 
      		 WHEN 111 THEN 111 
      		 WHEN 113 THEN 113 
      		 WHEN 114 THEN 114 
      		 WHEN 116 THEN 116 
      		 WHEN 117 THEN 117 
      		 WHEN 118 THEN 118 
      		 WHEN 120 THEN 120 
      		 WHEN 121 THEN 121 
      		 WHEN 122 THEN 122 
      		 WHEN 124 THEN 124 
      		 WHEN 125 THEN 125 
      		 WHEN 126 THEN 126 
      		 WHEN 127 THEN 127 
      		 WHEN 128 THEN 128 
      		 WHEN 129 THEN 129 
      		 WHEN 130 THEN 130 
      		 WHEN 131 THEN 131 
      		 WHEN 132 THEN 132 
      		 WHEN 134 THEN 134 
      		 WHEN 135 THEN 135 
      		 WHEN 136 THEN 136 
      		 WHEN 137 THEN 137 
      		 WHEN 138 THEN 138 
      		 WHEN 139 THEN 139 
      		 WHEN 140 THEN 140 
      		 WHEN 141 THEN 141 
      		 WHEN 142 THEN 142 
      		 WHEN 143 THEN 143 
      		 WHEN 144 THEN 144 
      		 WHEN 145 THEN 145 
      		 WHEN 146 THEN 146 
      		 WHEN 147 THEN 147 
      		 WHEN 148 THEN 148 
      		 WHEN 149 THEN 149 
      		 WHEN 150 THEN 150 
      		 WHEN 151 THEN 151 
      		 WHEN 152 THEN 152 
      		 WHEN 153 THEN 153 
      		 WHEN 154 THEN 154 
      		 WHEN 155 THEN 155 
      		 WHEN 156 THEN 156 
      		 WHEN 157 THEN 157 
      		 WHEN 158 THEN 158 
      		 WHEN 159 THEN 159 
      		 WHEN 160 THEN 160 
      		 WHEN 161 THEN 161 
      		 WHEN 162 THEN 162 
      		 WHEN 163 THEN 163 
      		 WHEN 164 THEN 164 
      		 WHEN 165 THEN 165 
      		 WHEN 166 THEN 166 
      		 WHEN 167 THEN 167 
      		 WHEN 168 THEN 168 
      		 WHEN 169 THEN 169 
      		 WHEN 170 THEN 170 
      		 WHEN 171 THEN 171 
      		 WHEN 172 THEN 172 
      		 WHEN 173 THEN 173 
      		 WHEN 174 THEN 174 
      		 WHEN 175 THEN 175 
      		 WHEN 176 THEN 176 
      		 WHEN 177 THEN 177 
      		 WHEN 178 THEN 178 
      		 WHEN 179 THEN 179 
      		 WHEN 180 THEN 180 
      		 WHEN 181 THEN 181 
      		 WHEN 182 THEN 182 
      		 WHEN 183 THEN 183 
      		 WHEN 184 THEN 184 
      		 WHEN 185 THEN 185 
      		 WHEN 186 THEN 186 
      		 WHEN 187 THEN 187 
      		 WHEN 188 THEN 188 
      		 WHEN 189 THEN 189 
      		 WHEN 190 THEN 190 
      		 WHEN 191 THEN 191 
      		 WHEN 192 THEN 192 
      		 WHEN 193 THEN 193 
      		 WHEN 194 THEN 194 
      		 WHEN 195 THEN 195 
      		 WHEN 196 THEN 196 
      		 WHEN 197 THEN 197 
      		 WHEN 198 THEN 198 
      		 WHEN 199 THEN 199 
      		 WHEN 201 THEN 201 
      		 WHEN 202 THEN 202 
      		 WHEN 203 THEN 203 
      		 WHEN 204 THEN 204 
      		 WHEN 205 THEN 205 
      		 WHEN 206 THEN 206 
      		 WHEN 207 THEN 207 
      		 WHEN 209 THEN 209 
      		 WHEN 211 THEN 211 
      		 WHEN 213 THEN 213 
      		 WHEN 214 THEN 214 
      		 WHEN 216 THEN 216 
      		 WHEN 217 THEN 217 
      		 WHEN 220 THEN 220 
      		 WHEN 221 THEN 221 
      		 WHEN 222 THEN 222 
      		 WHEN 223 THEN 223 
      		 WHEN 224 THEN 224 
      		 WHEN 226 THEN 226 
      		 WHEN 230 THEN 230 
      		 WHEN 231 THEN 231 
      		 WHEN 234 THEN 234 
      		 WHEN 242 THEN 242 
      		 WHEN 243 THEN 243 
      		 WHEN 244 THEN 244 
      		 WHEN 246 THEN 246 
      		 WHEN 248 THEN 248 
      		 WHEN 249 THEN 249 
      		 WHEN 250 THEN 250 
      		 WHEN 257 THEN 257 
      		 WHEN 265 THEN 265 
      		 WHEN 277 THEN 277 
      		 WHEN 282 THEN 282 
      		 WHEN 289 THEN 289 
      		 WHEN 290 THEN 290 
      		 WHEN 292 THEN 292 
      		 WHEN 297 THEN 297 
      		 WHEN 305 THEN 305 
      		 WHEN 312 THEN 312 
      		 WHEN 322 THEN 322 
      		 WHEN 326 THEN 326 
      		 WHEN 343 THEN 343 
      		 WHEN 371 THEN 371 
      		 WHEN 379 THEN 379 
      		 WHEN 421 THEN 421 
      		 WHEN 422 THEN 422 
      		 WHEN 452 THEN 452 
      		 WHEN 455 THEN 455 
      		 WHEN 486 THEN 486 
      		 WHEN 495 THEN 495 
      		 WHEN 497 THEN 497 
      	 END  WHERE  `pageid` IN (12,19,20,21,24,34,36,37,39,40,45,47,48,49,50,51,53,56,59,60,74,76,78,80,84,85,88,92,94,95,100,101,102,103,104,107,108,109,110,111,113,114,116,117,118,120,121,122,124,125,126,127,128,129,130,131,132,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,201,202,203,204,205,206,207,209,211,213,214,216,217,220,221,222,223,224,226,230,231,234,242,243,244,246,248,249,250,257,265,277,282,289,290,292,297,305,312,322,326,343,371,379,421,422,452,455,486,495,497);
      
      MySQL-Fehler  : Unknown column 'pageid' in 'where clause'
      Fehler-Nr.    : 1054
      Fehler-Zeit   : Tuesday, 09.06.2015 @ 19:19:46
      Datum         : Tuesday, 09.06.2015 @ 19:19:46
      Skript        : xxx/pride-test/admin_cp/wiki_cp.php?panel=impex&do=import&step=25&nostyle=1
      Referrer      : xxx/pride-test/admin_cp/wiki_cp.php?panel=impex&do=import
      IP-Adresse    : xxx
      Benutzername  : xxx
      Klassenname   : vB_Database
      MySQL-Version : 5.5.42-37.1-log
      
      Stack Trace:
      
      #0 vB_Database->halt() called in [path]/includes/class_core.php on line 426
      #1 vB_Database->execute_query() called in [path]/includes/class_core.php on line 444
      #2 vB_Database->query_write() called in [path]/vault/core/controller/db/vb3.php on line 186
      #3 vw_DB_Controller_vB3->query_write() called in [path]/vault/core/model/db/mysql/vw.php on line 950
      #4 vw_DB_MySQL_Model->shutdown_or_run() called in [path]/vault/core/model/db/mysql/vw.php on line 719
      #5 vw_DB_MySQL_Model->update() called in [path]/vault/core/controller/import/handle/vw3/popularity/vw.php on line 103
      #6 vw_Import_Handle_VW3_Popularity_Controller->do_popularity() called in [path]/vault/core/controller/import/steps/vw3/vw.php on line 558
      #7 {closure}() called in [path]/vault/core/controller/progress/vw.php on line 100
      #8 vw_Progress_Controller->call() called in [path]/vault/core/controller/cp/impex/vw.php on line 114
      #9 vw_CP_ImpEx_Controller->import() called in [path]/vault/core/controller/cp/impex/vw.php on line 35
      #10 vw_CP_ImpEx_Controller->execute() called in [path]/vault/helper/vb/global.php on line 66
      #11 require_once([path]/vault/helper/vb/global.php) called in [path]/admin_cp/wiki_cp.php on line 24
      Needles to say that this try didn't work. I could set up another (third) test board and see if it works there since it worked fine on the first test board. But that would be a little bit over the top, wouldn't it?
      Reply Reply
    8. June 10, 2015 8:31 AM
      pegasus pegasus is offline
      VaultWiki Team
      In vault/core/controller/import/handle/vw3/popularity/vw.php, find the function:
      Code:
      	public function do_popularity($startat)
      Replace the whole function with:
      Code:
      	public function do_popularity($startat)
      	{
      		$forummap = $this->get_import_forummap();
      
      		if (!$forummap)
      		{
      			return false;
      		}
      
      		$views = vw_DB::get($this->from)->query()->select(array(
      			'fields' => array(
      				'threadid',
      				'views'
      			),
      			'table' => 'thread',
      			'where' => array(
      				vw_DB::get($this->from)->query()->in('forumid', array_keys($forummap))
      			),
      			'order' => array('threadid' => 'ASC'),
      			'limit' => array($startat, 500)
      		));
      
      		$update = array();
      
      		if (vw_DB::get($this->from)->func()->num_rows($views))
      		{
      			while ($view = vw_DB::get($this->from)->func()->fetch_array($views))
      			{
      				if (!$view['views'])
      				{
      					continue;
      				}
      
      				$update[$view['threadid']] = $view['views'];
      			}
      			vw_DB::get($this->from)->func()->free_result($views);
      			unset($view);
      		}
      
      		$mapped = array();
      
      		if ($update)
      		{
      			$pagemap = $this->get_import_threadids(array_keys($update));
      
      			$routes = vw_DB::get()->query()->select(array(
      				'fields' => array(
      					'routeid',
      					'itemid'
      				),
      				'table' => 'vw_route',
      				'where' => array(
      					vw_DB::get()->query()->eq('itemtypeid', vw_Hard_Core::model('Node')->id('Page')),
      					vw_DB::get()->query()->in('itemid', $pagemap)
      				),
      				'limit' => count($pagemap)
      			));
      
      			while ($route = vw_DB::get()->func()->fetch_array($routes))
      			{
      				$threadid = array_search($route['itemid'], $pagemap);
      
      				if (!$threadid)
      				{
      					continue;
      				}
      
      				$mapped[$route['routeid']] = $update["$threadid"];
      			}
      			vw_DB::get()->func()->free_result($routes);
      		}
      
      		if ($mapped)
      		{
      			vw_DB::get()->query()->update(array(
      				'table' => 'vw_counter',
      				'set' => array(
      					'views' => array(
      						'case' => 'routeid',
      						'when' => $mapped
      					)
      				),
      				'where' => vw_DB::get()->query()->in('routeid', array_keys($mapped)),
      				'limit' => count($mapped)
      			));
      
      			return 500;
      		}
      
      		return false;
      	}
      After the replacement, you should notice that the next line you didn't replace is:
      Code:
      	public function do_pending($startat)
      Then please try to continue the current import and it should complete as expected.
      Reply Reply
    9. June 10, 2015 9:44 AM
      Kirauni Kirauni is offline
      Junior Member
      Thanks again, Pegasus! That did the trick. The import finished fine and now I'll have a look at the imported pages. If everythings looks all right, I'll try it again one last time on a backupboard and then move to my live version. Hopefully, that'll work, too. Thanks again for your help!


      Edit: Now this is strange... the skript told me that the import has been successful. I set up the rights properly, but when I clicked in the WIKI-Page, none of my three wikis have been listed. We're still talking about my second testboard and my second attempt. On my first testboard the import has been successful though. I don't know what's causing the difference here...

      Edit 2: I can see the three wikis in the area manager, but not on the actual wiki page. The images seem to have been imported, though.
      Reply Reply
    10. June 11, 2015 8:17 AM
      pegasus pegasus is offline
      VaultWiki Team
      In the Area Manager, check the Display Order for the "missing" areas. The Display Order might be set to 0, which hides them.
      Reply Reply
    11. June 11, 2015 1:32 PM
      Kirauni Kirauni is offline
      Junior Member
      Ah thanks again! That worked. I don't know how I could miss that

      There are still some issues that I could need help with:

      1.)
      Now there's a prolem with certain images that are not displayed properly. So I wanted to edit the article and have a look at the image-code. However, when I clicked on "Edit" the Editor opened and all the article's text just vanished... When I saved it, there was no text in the article left. Is this a bug or a feature? It also happend with an article I've newly created.

      2.)
      And there's another thing. I used some tags on the old articles like a year or an artist's name. Back in vw3 you could click on one of those tags and display all other articles that use the same tag. When I checked this in my import, I was not able to click on the tags. Only the categories are clickable. Have the tags been removed completely or am I missing another setting?


      3.)
      Are tables in an article allowed in vw4? Because I've used some tables in my vw3 articles and now they just appear as plain codes and not as a real table. --> Okay, I somehow fixed it by tweaking the codes in the syntax manager. Now it appears to work.

      4.)
      The Wiki-Codes don't work properly. The whole "code" [wikiname=articlename]mytexthere[/wikiname] is visible and not just the link. However "mytexthere" is a link... that's looking quite strange and it's hard to explain. It looks like the bbcode of one wiki went missing and I haven't found out how to replace it yet.

      Edit: Okay I think I got it... back in vaultwiki 3 there was a slightly different syntax and I guess I have to use [wikiname="articlename"]mytexthere[/wikiname]. That also means I'll have to edits tons of links myself or somehow find/write a skript that does that.

      5.)
      About the prefixes... In vw3 I used many prefixes like (Comic) or (CD), etc. I always had to add the prefix in a code like
      [wikiname=articlename (prefixname)]mytexthere[/wikiname] or [wikiname]Articlename (prefixname)[/wikiname] or in terms of a URL:
      http://www.domainname/showwiki.php?t...clename_prefix.
      I've just read in the documentation that this is no longer necessary. So that means I'll also have to replace all these old links, too?
      I see a lot of work ahead of me and I'm not even working on my live site *lol* I think it would have been easier to copy all my articles myself than using the importer, because I have to edit every single article anyway... or am I missing something?

      Sorry to be such a bother, but I really like VaultWiki and I'd love to keep it on my site
      Reply Reply
    12. June 12, 2015 8:23 AM
      pegasus pegasus is offline
      VaultWiki Team
      1 & 2) These sound like bugs. I would like to check out what you are experiencing but it seems your new test board has moved to a different location. Please submit a new ticket using the same method as before. The editor contents disappearing is actually a vBulletin bug that I reported to them over 3 years ago but we can probably work around it if I can see what triggers it on your site.

      4) Make sure that your default wiki code is set to what it was in VW3 and isn't the VW4 default (WIKI). It's under Settings > Wiki Links. There might be a similar issue with your images (VW3 code was IMAGE, VW4 default is FILE). Resolving this should be as simple as changing the appropriate settings back to the VW3 values, then erasing the wiki's post cache in Integrity > Counters.

      5) The kind of Prefixes you are talking about were "Thread Prefixes". They are not premade anymore, but you are still welcome to use them in your naming and it won't have a negative effect. You don't have to remove them from existing pages.

      VW4 renamed "Namespaces" to the word "Prefixes." Unless you make your area settings require a prefix, those are no longer necessary. But again you don't have to change anything about your previous data.
      Reply Reply
    13. June 12, 2015 11:42 AM
      Kirauni Kirauni is offline
      Junior Member
      Quote Originally Posted by pegasus
      1 & 2) These sound like bugs. I would like to check out what you are experiencing but it seems your new test board has moved to a different location. Please submit a new ticket using the same method as before. The editor contents disappearing is actually a vBulletin bug that I reported to them over 3 years ago but we can probably work around it if I can see what triggers it on your site.
      A bug with vBulletin's editor? Wow... bad luck again. You're right, you're currently not able to see it for yourself. As I've mentioned earlier, this is the second testboard now. I'll fill out the form as soon as possible. Thanks

      Quote Originally Posted by pegasus
      4) Make sure that your default wiki code is set to what it was in VW3 and isn't the VW4 default (WIKI). It's under Settings > Wiki Links. There might be a similar issue with your images (VW3 code was IMAGE, VW4 default is FILE). Resolving this should be as simple as changing the appropriate settings back to the VW3 values, then erasing the wiki's post cache in Integrity > Counters.
      Thanks, that worked. At least it did for the "Default Link Tag". I replaced it with one of my wiki's tags. However, I do have three different wikis and each one has its own tag ([ahadi], [kdl] and [plwiki]). Is there a way to "tell" vw4 to recognise the other two tags as well?
      Oh and yes, the images are working fine now

      Quote Originally Posted by pegasus
      5) The kind of Prefixes you are talking about were "Thread Prefixes". They are not premade anymore, but you are still welcome to use them in your naming and it won't have a negative effect. You don't have to remove them from existing pages.
      VW4 renamed "Namespaces" to the word "Prefixes." Unless you make your area settings require a prefix, those are no longer necessary. But again you don't have to change anything about your previous data.
      All right... That's a bit confusing, but I'll try to figure it out and see how that goes. Thanks again
      Reply Reply
    14. June 12, 2015 2:09 PM
      pegasus pegasus is offline
      VaultWiki Team
      The other wikis tags were set for specific namespaces. Check the new prefix manager for the corresponding prefix and make sure they have the tag you expect in the prefix settings. I will look at the editor issue shortly
      Reply Reply
    15. June 13, 2015 11:18 AM
      pegasus pegasus is offline
      VaultWiki Team
      I have added a workaround for the vBulletin editor bug to a new build of 4.0.4. There are other ways to trigger the bug, but the way it was triggered before should not happen anymore.

      Also, when you do your live import, I recommend making sure all your settings are correct before the import. Specifically importing with the wrong "Replaces Spaces in URLs" setting and changing it later can cause issues.
      Reply Reply
    Page 1 of 2 12 Next LastLast
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 11:19 PM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.