Issue: Browser error: Failed to decode downloaded font

Issue Tools
- View Changes

July 30, 2015 6:27 PM

Desita

Junior Member

Browser error: Failed to decode downloaded font

Got everything up and running and it was going pretty well, but for reasons unknown to me, the fonts have stopped being read/parsed by my browsers. Chrome, Firefox, and Opera.

This is what chrome says: http://i.imgur.com/bIb6wWk.jpg

It seemed fine at first (at least on chrome), but now the images related to vw itself have stopped showing up.

Aside from this, I'd also like to know how to change the url from "wiki_index" to just "wiki".
So that:
example.club/wiki_index/Angelic-Saga
becomes
example.club/wiki/Angelic-Saga

I use dbseo, but my attempts at rewriting this have all failed.

Issue Details

Issue Number 4356

Issue Type Bug

Project VaultWiki 4.x Series

Category Images / Icons

Status Fixed

Priority 4 - Warnings / Script Errors

Affected Version 4.0.5

Fixed Version 4.0.6

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 vbulletin 4.2.2

July 31, 2015 7:46 AM

pegasus

VaultWiki Team

In the wiki settings panel for "Site Config", your Wiki Base URL probably starts with //

In vault/core/model/url/vw.php, find:

Code:

$prots = explode('://', $this->base["$type"], 2);

After it, add:

Code:

			if (!isset($prots[1]) AND strpos($this->base["$type"], '//') === 0)
			{
				$prots = array(
					'',
					substr($this->base["$type"], 2)
				);
			}

July 31, 2015 1:35 PM

Desita

Junior Member

I tested out adding that code, but it broke the wiki url link entirely All it did was remove my domain name from the url. When going to it, it changed the url in my browser to only /wiki_index/

These are my config settings
http://i.imgur.com/GJ2L5kk.jpg

Reply
July 31, 2015 3:05 PM

pegasus

VaultWiki Team

I only see that behavior occurring if you erased the original find code, instead of adding after it. Even so, the change would have no effect for you since it only applies if your base URL starts with // and nothing before it. I don't think VaultWiki is doubling the domain based on your settings. It is possible that DBSEO is trying to change it to an absolute URL because it appears relative without the protocol. To confirm I would have to look at DBSEO's code. If you would like, please submit a Ticket Support from the Services category on our Members tab, and I will try to find out what code is adding the second domain.

Reply
July 31, 2015 5:48 PM

Desita

Junior Member

I'm not sure what has changed, but maybe some configuration I edited caused the software to correct itself. It seems all the fonts are now working correctly again. If it stops working again then we can investigate it later? It wasn't hindering the software itself from what I could tell. Everything worked, just the image icons were not displaying.

Otherwise, any idea if I can change the url scheme? I just want the urls to say "/wiki/*" instead of "/wiki_index/*".

Reply
July 31, 2015 9:32 PM

pegasus

VaultWiki Team

Even if it works, the domain is still doubling. I see this in your CSS: //example.club//example.club/vault/resources/fonts/font-awesome/fontawesome-webfont.eot
So if it stops working again, it is most likely due to this.

To change the URL term you have to change the setting "Filename of the Wiki PHP file"
Then you have to update the .htaccess rules for the wiki and change the wiki_index stuff to the new name. I think there is another block that needs to be activated, but the .htaccess comments should explain this.

I am leaving this open for now, since VaultWiki has the same fault as DBSEO of adding the domain before // in a few places if // is used to start the base URL (your base URL isn't like this, so you are not affected by the VaultWiki fault).

Reply
August 1, 2015 12:05 AM

Desita

Junior Member

Well, I tried everything I could find regarding instructions on changing this. I'm not sure if maybe dbseo was interfering or not, but I changed it everywhere both you and the htaccess comments said I should. Best I got it to do was give em the /wiki/ in address bar, but it still gave a 404 page stating it couldn't find wiki_index.php
I'm sure I'm doing something terribly wrong and am just too dumb to see it.

And I'm not sure if it would help you look into that double url issue or not, but you can get the free version of DBSeo from their website at http://www.dragonbyte-tech.com/produ...ragonbyte-seo/

Reply
August 1, 2015 9:01 AM

pegasus

VaultWiki Team

You did not actually rename wiki_index.php, right?
The file should still have wiki_index.php as it's name on the server.

Reply
August 1, 2015 2:47 PM

Desita

Junior Member

No. I change the name in the config settings, and then I edit the htaccess line and uncomment it as it says.

After that, the wiki navbar link reads /wiki/ when hovering over it, but it still tries to go to /wiki_index/ and tosses a 404 error.

Reply
August 1, 2015 6:36 PM

pegasus

VaultWiki Team

Sounds like the wiki cache is not updated with the change yet. It is possible you have other items in your deferred.php queue ahead of it. You can rebuild it manually by going to the wiki admin > Maintenance > Rebuild Counters / Cache > Rebuild Page URLs option. However, you might not be able to re-enable "Wiki Active" in the Site Config until the deferred.php action completes.

Reply
August 1, 2015 8:12 PM

Desita

Junior Member

That was the problem, thank you!

Was skeptical at first, but quite enjoying this product so far.

Reply

+ Reply

All times are GMT -4. The time now is 6:31 AM.

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

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

Issue: Browser error: Failed to decode downloaded font

Issue Tools