3,554
edits
Talk:Main Page: Difference between revisions
Jump to navigation
Jump to search
Want an adless experience? Log in or Create an account.
no edit summary
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Add Spin-off Titles to Main Navigation Page == | == Add Spin-off Titles to Main Navigation Page == | ||
| Line 44: | Line 41: | ||
:But that's not the point. I think I know where the issue lies here...Phantom Ganon's sword doesn't really have a tip, per say, like most normal swords do. It's just a big block of blade. When the sword falls to the ground it lands with the smallest part of the sword pointing away from you; in this case the hilt, which pretty much looks like a point or tip compared to the rest of the sword. Regardless, I've updated it to use hilt instead. {{:User:Josh/sig}} 13:33, May 15, 2016 (UTC) | :But that's not the point. I think I know where the issue lies here...Phantom Ganon's sword doesn't really have a tip, per say, like most normal swords do. It's just a big block of blade. When the sword falls to the ground it lands with the smallest part of the sword pointing away from you; in this case the hilt, which pretty much looks like a point or tip compared to the rest of the sword. Regardless, I've updated it to use hilt instead. {{:User:Josh/sig}} 13:33, May 15, 2016 (UTC) | ||
== Glitch == | |||
There's a glitch on the tabs. Sometimes when I go to a page with a tab box on it, the tabs appear as normal text and I can't go to the other sections of the tab box. Is it possible to fix that glitch? [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:14, May 12, 2016 (UTC) | |||
:Please put new talk sections at the bottom of the page. It confuses people and makes it considerably less likely to be noticed or answered. Anyway, this is a known issue however it's not on our end. This is a problem with the web browsers, not our tabs. And therefore, it cannot be "fixed" by us. Sometimes they just don't load a script. It's more common with more complicated scripts. But not necessarily longer or bigger scripts, rather more so ones performing complicated tasks and to even do what they have to do, and a tabs script needs to do some fairly complicated tasks because it's altering how the page itself looks dynamically. | |||
:The only way around this is for the functions to be replaced with more efficient PHP coding, but so far none exists for a wiki platform that can do the things we need. Existing tabs interfaces available on MediaWiki (our, and the most commonly used, wiki software) are very, very simple and are not as customizable, fluid, flexible, or anywhere near as useful as the script we use. We would severely limit what we can do with toggling functions (like tabs) if we used a lesser PHP function that didn't include the same capabilities. So we have to use the scripts and just deal with the browser-side issues. Besides, it'd still be an intensive function PHP, and it would vastly increase our server load, which is why most sites still use scripts for so many things like this. Just can't afford that server load. So, again, scripts. | |||
:This happens on every website. You probably usually don't notice it most of the time because most scripts that fail do things you probably would never notice. Scripts load on your end, not our server's end. If you load up your browser's console or inspect element form while browsing the net, you'll get notices of failed scripts all over the net on a fairly regular basis. If the script doesn't load for you, try just refreshing the page. If it still isn't up, you can refresh or clear your cache. It also can help by reducing your browser's memory load by closing tabs or suspending them (for instance you can temporarily suspend tabs with the extension called The Great Suspender). | |||
:Your computer needs enough resources to properly load a script and run it. The tabs script's issue is the tasks it's trying to do, things like that can have this error but it needs to do those things to accomplish its task so there's little we can change to the script. Problems like this are more common on lower end PCs but you can manage it them fairly easily with the extension I mentioned or similar ones on Firefox But I suggest switching to Chrome if you are using Firefox (or anything else) because it is more stable and has less trouble loading scripts, though this still happens on it. If you're editing on tablet or smartphone, you'd have to do things like closing other open programs you have running and closing other tabs. | |||
:Probably a longer explanation than you were looking for but I wanted to fully cover the entire topic so there was no confusion.— {{User:Matt/Sig}} 07:27, June 15, 2016 (UTC) | |||