Jump to content


Help Wanted

  • Please log in to reply
16 replies to this topic

#16 z929669


    Ixian Inventor

  • Administrator
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 7,082 posts

Posted 15 March 2013 - 12:08 AM

Cap was set at 50 and this was a global MW setting, no?

#17 stoppingby4now



  • Founder
  • PipPipPipPipPipPip
  • 2,419 posts

Posted 16 March 2013 - 12:43 AM

[quote name=''z929669' pid='29979' dateline='1363324085']Cap was set at 50 and this was a global MW setting' date=' no?[/quote']
You are probably thinking of the standard result limitation before it automatically adds the more results link. That setting should not be touched. That can be thought of as a soft cap. There is also a hard cap which is what I am referring to, and that is much higher.

To add to this, there are several mod pages I'm seeing that need to have their pages re-saved regardless, as they haven't been updated with the new mod page layout.

Example of good page layout: https://wiki.step-pr...Script_Extender
Example of bad page layout: https://wiki.step-pr...mproved_Torches (at least until it's updated)

The pages that need updating are very easy to spot.
  • Go to a Category page (i.e. Category:ModSection_F)
  • From the PAGE TOOLS menu, select REFRESH.
  • Scan the list of mods and look for entries where the Core: label has no value.
  • Open the relevant mod pages and...
    • From the PAGE TOOLS menu, select EDIT WITH FORM.
    • Click the [Save] button at the bottom of the page.
  • Once all mod pages have been updated within a category, visit the Category page again, select the PAGE TOOLS menu, and select REFRESH to force an update of the semantic data.
  • Verify that all mod entries on the Category page have either a true or false value for the Core: label.

  • 0

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users