FANDOM


  • Can someone help sort this problem out?

      Loading editor
    • What is the problem?

        Loading editor
    • Code access not working

        Loading editor
    • What do you mean by "code access"? It looks like you haven't even installed the script yet.

        Loading editor
    • How is it installed?

        Loading editor
    • Follow the instructions here. To do what they instruct, you will need to enable site JS. You can do so by contacting staff. It may take a few days for them to get to your ticket.

        Loading editor
    • Now that custom JS has been enabled, you should be able to just follow the directions in the script documentation.

        Loading editor
    • On that wiki? Where?

        Loading editor
    • Follow the "here" link in the 3rd post above this one.

        Loading editor
    • I meant on my wiki, not the developer one

        Loading editor
    • Import the script here and set the log page here. Since you need to submit the latter for approval, do that first and wait until it is approved before importing the script.

        Loading editor
    • Andrewds1021 wrote: Import the script here and set the log page here. Since you need to submit the latter for approval, do that first and wait until it is approved before importing the script.

      I don’t know what happened, but I accidentally did the reverse and the WAM log still showed up without the approval process.

        Loading editor
    • Yes, it will work. However, the logging function won't save data to the correct page. Right now, each user that clicks the log button will store their own separate copy. So if 5 different users do it, 5 different copies will be created. What the part in Common.js does it specify a common page such that there is only one copy for the entire wiki. Also, you can set it to autolog the data for you so you don't even have to press the button.

        Loading editor
    • I also noticed that it’s hidden from view, does that happen because the common JavaScript isn’t added?

        Loading editor
    • You mean the actual data? That is intentional. The extension doesn't format the data in a human-friendly format.

        Loading editor
    • The processing on the JavaScript (common) is.... way too long, any reason for that?

        Loading editor
    • Because there are staff members on the other end that are literally inspecting the JS before approving it.

        Loading editor
    • What do they look for? Accuracy? Or something else?

        Loading editor
    • Security risks and policy violations.

        Loading editor
    • Okay, do they recommend removal after the code is added, to prevent security breaches?

        Loading editor
    • I am not sure what you mean by "removal". Staff look at the JS and if they determine it is not suitable, they can do one of two things.

      If they see a quick fix, they may do that for you and then immediately approve their modified version. On a few occasions, I have seen them do this for simple syntactical errors as well. However, this is not a service they have promised to provide. There have been a few times that I have made a mistake and it got approved.

      Otherwise, they will simply mark it as rejected and the most recent approved revision will be used instead. Typically they will provide a reason for the rejection so you can try to correct it and resubmit for approval.

        Loading editor
    • By removal, I mean clearing the JavaScript each time a change is resolved.

        Loading editor
    • I still don't quite get where you are coming from. A wiki only uses the most recently approved revision of a JS page. When staff reject a revision, nothing happens to the page itself.

        Loading editor
    • In other words, don't confuse what you see currently on the JS page with what is actually being executed for the wiki.

      The current version of the Common.js page will only get used if you see something like the following in the right side bar:

      Latest revision:
            #<some#> is live!
        Loading editor
    • https://viacomcbs.fandom.com/wiki/MediaWiki:Wikia.css

      Did I miss any codes here? If yes, can you provide them?

        Loading editor
    • We're not psychic.

        Loading editor
    • Oh my bad @Fandyllic

      However I eventually figured out the process

        Loading editor
    • FYI, I went ahead and copied the previous day's data from your personal log to the wiki's log. If you don't want extra pages laying around, you can go ahead and delete your log and Monstermon's log. Neither will be used now that the wiki's log is the target. Also, there are additional settings you can set so that it automatically logs the data when either of you access the wiki. That way, you don't need to remember to click the button each time. You do need to visit the wiki though. If you are interested, you can enable it by editing your site's JS to be like this:

      window.railWAM = {
          logPage: "Project:WAM Log",
          autoLogForUsers: [
              "Monstermon",
              "UpnCbs06"
          ]
      }

      Edit:

      Of course, the new version would need to be approved before it becomes active. In the mean time, you will still need to click the button.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.