Weird view of Installer Page

Hello @Ange Tuteur,

Today i noticed the new update notification and i went to my installer page to check and update the theme but, it appears that the Installer Page has some "bugs"..
See other times i did this it was fine but today it just doesn't show me almost anything.
Here's a screenshot of what i see once i view my installer : http://prntscr.com/cz9yl5

I do not have any clue why this is happening since the code has stayed the same and nothing was changed...
The page is /22-installer but i believe you have Admin powers to check it.
If you need owner account access please let me know.. Thanks!

Hi @Luffy,

I believe the cause of the control panel not working is a javascript error on your forum.


The query to document.getElementId returned null since it couldn't find "table#ys". It's usually good to check if an element is null or not before using it. For example :

Code:

var table = document.getElementById('table#ys');

if (table) {
  table.insertAfter('.module:nth-child(2)');
}

That way you wont get any errors. Still there's a few reasons for this error :

1. The reason it returned null is because a query string was used ( table#ys ), when an id string without the hash should only be used in getElementById ; 'ys'.
2. There's no "insertAfter" method in pure javascript, this does exist in jQuery though. In pure JS you can use insertBefore, appendChild, insertAdjacentHTML, etc..

Sorry for the lecture lol. Anyways, you can also resolve the issue by changing it to the jQuery equivalent, since that's what it looks like it's written for.

Code:

$('table#ys').insertAfter('.module:nth-child(2)')

If the CP doesn't work after resolving this error let me know.

Ange i don't know what to change but anyway you can close this thread as Think Tank is closing.

Thanks for your help.

Oh I see, that's sad to hear..

Anyway from what I could tell an error was caused by this script :

Code:

$(function(){$(function(){document.getElementById('table#ys').insertAfter('.module:nth-child(2)')});});

Either removing it or applying the fix I mentioned would've resolved the error.

That solved the issue. Thanks!

No problem. Hope you have a good weekend. ^^