3,554
edits
Want an adless experience? Log in or Create an account.
m
Text replacement - "User:Matt" to "User:Emma"
No edit summary |
m (Text replacement - "User:Matt" to "User:Emma") |
||
| Line 11: | Line 11: | ||
<br/> | <br/> | ||
Correction: I'm not the only user editing, but not many people are editing. [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:26, May 9, 2016 (UTC) | Correction: I'm not the only user editing, but not many people are editing. [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:26, May 9, 2016 (UTC) | ||
:Most wikis slow down over time. Especially small ones. It's part of the process. We're expecting a surge of activity when the next console game is released. In the meantime though, announcements on the main page asking people to edit really aren't going to help. Instead I've already suggested some other promotions we can try in our staff chat. We'll see where those go. It's been uncomfortably slow for a while.— {{User: | :Most wikis slow down over time. Especially small ones. It's part of the process. We're expecting a surge of activity when the next console game is released. In the meantime though, announcements on the main page asking people to edit really aren't going to help. Instead I've already suggested some other promotions we can try in our staff chat. We'll see where those go. It's been uncomfortably slow for a while.— {{User:Emma/Sig}} 14:49, May 10, 2016 (UTC) | ||
I hope the editing speeds up son. [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:14, May 12, 2016 (UTC) | I hope the editing speeds up son. [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:14, May 12, 2016 (UTC) | ||
| Line 33: | Line 33: | ||
Just a few suggestions and mistakes. Hope this helped~ TattooArtist ^_^{{Unsigned|TattooArtist|19:38, May 9, 2016}} | Just a few suggestions and mistakes. Hope this helped~ TattooArtist ^_^{{Unsigned|TattooArtist|19:38, May 9, 2016}} | ||
:In the future, please sign your posts by simply typing four tilde characters (this: <b><nowiki>~~~~</nowiki></b>) instead of typing out your name. Just those characters, don't add your name to it. This helps clearly differentiate posters and help tell when posts were made. I'll forward this to our walkthrough people. That's really their area.— {{User: | :In the future, please sign your posts by simply typing four tilde characters (this: <b><nowiki>~~~~</nowiki></b>) instead of typing out your name. Just those characters, don't add your name to it. This helps clearly differentiate posters and help tell when posts were made. I'll forward this to our walkthrough people. That's really their area.— {{User:Emma/Sig}} 14:49, May 10, 2016 (UTC) | ||
There's also an error in the Wind Waker walkthrough. After the battle with Phantom Ganon in Ganon's Castle, Phantom Ganon drops his sword. Then, Link needs to enter the door that the sword's blade is pointing to. But the walkthrough said to drop it in the center of the room, which shouldn't be done, and to follow the hilt, which leads to the wrong door. Can you please tell the walkthrough people about this? [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:05, May 12, 2016 (UTC) | There's also an error in the Wind Waker walkthrough. After the battle with Phantom Ganon in Ganon's Castle, Phantom Ganon drops his sword. Then, Link needs to enter the door that the sword's blade is pointing to. But the walkthrough said to drop it in the center of the room, which shouldn't be done, and to follow the hilt, which leads to the wrong door. Can you please tell the walkthrough people about this? [[User:ZD Wiki Editor|ZD Wiki Editor]] ([[User talk:ZD Wiki Editor|talk]]) 05:05, May 12, 2016 (UTC) | ||
| Line 57: | Line 57: | ||
: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). | :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. | :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: | :Probably a longer explanation than you were looking for but I wanted to fully cover the entire topic so there was no confusion.— {{User:Emma/Sig}} 07:27, June 15, 2016 (UTC) | ||
::Sorry, I just started using the talk pages, so I didn't know about the formatting. And you have a point about the errors. Whenever I use Inspect Element, there are always around 10 errors. Also, I'm using Chrome on my computer, but reloading doesn't work. Neither does closing other tabs. I haven't tried clearing my cache yet, and The Great Suspender seems useful. Thanks for the explanation! It may be long, but at least it's not vague. [[User:ZD Wiki Editor|Zelda]] ([[User talk:ZD Wiki Editor|talk]]) 23:57, July 2, 2016 (UTC) | ::Sorry, I just started using the talk pages, so I didn't know about the formatting. And you have a point about the errors. Whenever I use Inspect Element, there are always around 10 errors. Also, I'm using Chrome on my computer, but reloading doesn't work. Neither does closing other tabs. I haven't tried clearing my cache yet, and The Great Suspender seems useful. Thanks for the explanation! It may be long, but at least it's not vague. [[User:ZD Wiki Editor|Zelda]] ([[User talk:ZD Wiki Editor|talk]]) 23:57, July 2, 2016 (UTC) | ||
:::Please don't remove old conversations. I'm not sure you intended to do that. Try using the show preview button whenever you edit a page from now on. Especially talk pages. Then you'll notice if it did something you weren't trying to do. Chrome should be able to handle the site just fine if you take the steps I recommended. They shouldn't be necessary on a typical, modern computer less than a year or two old. But if you have an old dinosaur PC like mine, those steps I outlined would help a lot. It is entirely normal to be a handful of errors on inspect element. Most of the time they are absolutely harmless and will go by unnoticed. Usually, it's something in the background that doesn't make visible changes so it won't affect your experience. And in Chrome, often the script will run anyway despite the error because it has built-in solutions to compensate for that. It doesn't work 100% of the time but it often will work. | :::Please don't remove old conversations. I'm not sure you intended to do that. Try using the show preview button whenever you edit a page from now on. Especially talk pages. Then you'll notice if it did something you weren't trying to do. Chrome should be able to handle the site just fine if you take the steps I recommended. They shouldn't be necessary on a typical, modern computer less than a year or two old. But if you have an old dinosaur PC like mine, those steps I outlined would help a lot. It is entirely normal to be a handful of errors on inspect element. Most of the time they are absolutely harmless and will go by unnoticed. Usually, it's something in the background that doesn't make visible changes so it won't affect your experience. And in Chrome, often the script will run anyway despite the error because it has built-in solutions to compensate for that. It doesn't work 100% of the time but it often will work. | ||
:::Also, on talk pages it's usually preferred that when you respond to something you indent your reply. Do that by typing one colon at the start of your post, like you see on mine here in the edit view, for each time you indent (I indented your reply so you can see what I mean). So two colons to indent two levels, and so on. And leave a reply without any indent at all after... I'd say three replies, usually, have been indented. That keeps things easier to read. Indented replies also let you make clean paragraphs quick and easy like this.— {{User: | :::Also, on talk pages it's usually preferred that when you respond to something you indent your reply. Do that by typing one colon at the start of your post, like you see on mine here in the edit view, for each time you indent (I indented your reply so you can see what I mean). So two colons to indent two levels, and so on. And leave a reply without any indent at all after... I'd say three replies, usually, have been indented. That keeps things easier to read. Indented replies also let you make clean paragraphs quick and easy like this.— {{User:Emma/Sig}} 05:59, July 3, 2016 (UTC) | ||
And here I am just saying something else and signing it again, at the same time, to show a base level with no indentation again, so the next reply should be indented. It took me a while to get used to this, but really it becomes second nature pretty fast and it really smooths things up.— {{User: | And here I am just saying something else and signing it again, at the same time, to show a base level with no indentation again, so the next reply should be indented. It took me a while to get used to this, but really it becomes second nature pretty fast and it really smooths things up.— {{User:Emma/Sig}} 05:59, July 3, 2016 (UTC) | ||