FANDOM


<hubspopularvideos> Resident Evil's Alice Worst Friend Ever!|Ericmoro|||http://residentevil.wikia.com/Resident_Evil_Wiki Mighty Morphin Power Rangers Season 1, Vol.1 (2012) - Home Video Trailer for Mighty Morphin Power Rangers Season 1, Vol.1|Ericmoro|||http://powerrangers.wikia.com/wiki/The_Morphin_Grid:_A_Power_Rangers_Wiki Wreck-It Ralph (2012) - Theatrical Trailer 2 for Wreck-It-Ralph|Ericmoro|||http://wreckitralph.wikia.com/wiki/Wreck-It_Ralph_Wiki Batman The Dark Knight Returns, Part 1 (2012) - Home Video Trailer for Batman The Dark Knight Returns, Part 1|Ericmoro|||http://batman.wikia.com/wiki/Batman:_The_Dark_Knight_Returns_Part_1_%28film%29 Taken 2 (2012) - Featurette Family To Root For|Ericmoro|||http://movies.wikia.com/wiki/Taken_2 Texas Chainsaw 3D Trailer|Ericmoro|||http://horror-movies.wikia.com/wiki/Horror_Film_Wiki Boardwalk Empire Clip - Bid Adieu to 22|Ericmoro|||http://boardwalkempire.wikia.com/wiki/Boardwalk_Empire_Wiki Universal Soldier Day of Reckoning (2012) - Theatrical Trailer for Universal Soldier Day of Reckoning|Ericmoro|||http://universalsoldier.wikia.com/wiki/Universal_Soldier_Wiki Indiana Jones Blu-ray Set - Indy Gets Punched|Ericmoro|||http://indianajones.wikia.com/wiki/Main_Page </hubspopularvideos>


Please leave your notes while working with PLB here.

File:Step Up 4 (2012) - Theatrical Trailer for Step Up 4


Using Builder to Create LayoutsEdit

  • when trying to delete a layout, the following error occurs:
PHP fatal error in /usr/wikia/deploy/code/src/release-008.048/extensions/wikia/PageLayoutBuilder/PageLayoutBuilderModel.class.php line 226:


Call to a member function getNamespace() on a non-object

Abbott 05:19, February 16, 2011 (UTC)


Should be fixed as of yesterday. Kirkburn (talk) @fandom 19:57, February 17, 2011 (UTC)
  • apostrophes show up as code on the create page. I've used ’ as a special character as a temporary fix. —Scott 19:50, February 1, 2011 (UTC)
  • If I enter a category in the layout builder, pages created with that layout will go in that category. However if I edit the layout, the category is gone. If I don't add it back in again, when any page that was created using that layout is saved again, it's no longer in that category. —Scott 19:51, February 1, 2011 (UTC)
    • It is intended/known that the layout category won't show (fixing would be a feature request), but I can't reproduce losing the category. Can you point me to any examples? Kirkburn (talk) @fandom 14:02, February 11, 2011 (UTC)
  • special tags such as <includeonly> don't work and are stripped out of the layout. —Scott 19:54, February 1, 2011 (UTC)
    • What kind of things would you use them for? (It's complex to deal with) Kirkburn (talk) @fandom 14:44, February 11, 2011 (UTC)
  • Special:LayoutBuilder has a column for #Pages, which I assume is supposed to be the number of pages using that layout. However, the number doesn't link to anything, and it's provably false. —Scott 20:19, February 1, 2011 (UTC)
    • Got an example where the number is incorrect? (See point above for the rest) Kirkburn (talk) @fandom 14:07, February 11, 2011 (UTC)
  • Using templates aren't necessary to create layouts. Any code that's in a template that has traditionally been used on Wikia in the past can be incorporated into the code of a layout, without having to call up the template separately. For example, Layout:Episode Layout 001 was built using code from this template while Layout:Character is calling up Template:Character infobox. As a result, Layout:Character doesn't have the full benefits of the layout builder such as adding an image. —Scott 21:46, February 1, 2011 (UTC)
  • There is no instruction given for how to incorporate a template into the layout when creating it. Your average admin probably won't know how to correctly make use of an infobox or other template in the layout builder. Approaching the builder from the perspective of someone who is familiar with only basic Wikia markup, it would be helpful if there were simple directions to use the raw code from a template with Input Boxes for the sections that would normally draw from user-entered info - rather than trying to call the template into the builder using it's {{}} tag and original {{{}}} user input method. v

Using Layouts to Create PagesEdit

  • Overall comments are that using a uniform templates is a great idea and being able to just fill in questions asked is a much easier way for beginning users to feel comfortable and not intimidated by the process of inputting info to their wikis. Peter
  • Finish button in photo gallery builder not working repeatedly. Cannot select photos, though it does save them even though it appears it doesn't. Peter
    • Still an issue? Kirkburn (talk) @fandom 14:59, February 11, 2011 (UTC)
  • Received following error messgage: "Please correct the following errors: plb-special-form-none-value" when haven't filled in all the required fields yet. Peter
    • Should now be fixed. Kirkburn (talk) @fandom 14:59, February 11, 2011 (UTC)
  • I like that you have to have a minimum amount of info to create page, but would be much easier to upload a file rather than have to find the file name and add it manually. Peter
    • Not sure what you mean exactly - you should be able to upload new files and use existing ones. Kirkburn (talk) @fandom 14:59, February 11, 2011 (UTC)
  • when you enter page breaks in the input field, they don't show up on the saved article. —Scott 19:51, February 1, 2011 (UTC)
    • I'm not sure what you mean. A br in a single line field works (though is not the point of the field). Single line breaks in a multiline field don't show up because its a wikitext input area. Kirkburn (talk) @fandom 15:27, February 11, 2011 (UTC)
  • when you choose a picture, the image upload tool asks you for the layout which can be misleading if the layout is already being determined in the layout builder. —Scott 19:51, February 1, 2011 (UTC)
  • What if people want to add additional sections to the episode template such as music, quotes, etc.in addition to the given sections? Kate.moon 19:59, February 1, 2011 (UTC)
    • Yeah, we're looking into adding some flexibility of that sort. Kirkburn (talk) @fandom 15:11, February 11, 2011 (UTC)
  • transitioning an existing template from one wiki to another for characters, episodes...intuitive? Kate.moon 19:59, February 1, 2011 (UTC)
    • Interesting thought. Atm it would require going to the layout and copying the code - we could probably make this easier. Kirkburn (talk) @fandom 15:11, February 11, 2011 (UTC)
  • When a field has been set to Required and that field hasn't been filled out, it returns code that will be confusing to the editor. —Scott 20:13, February 1, 2011 (UTC)
    • Should now be fixed. Kirkburn (talk) @fandom 15:11, February 11, 2011 (UTC)
  • When the required field isn't filled out, it doesn't let the editor save the page and go back to it (I tried it with pictures) Kate.moon 20:15, February 1, 2011 (UTC)
    • You'd want some kind of draft saving functionality? (If required fields aren't required, what are they? :P ) Kirkburn (talk) @fandom 15:11, February 11, 2011 (UTC)
      • In case someone wanted to come back to the page later it would be helpful if they could save the work they've done, so they don't have to start from scratch the next time. As long as they aren't able to publish the unfinished work, I think they should be able to save their work even if they haven't field out the required fields. Kate.moon 18:08, February 11, 2011 (UTC)
  • Screen shot 2011-02-01 at 1.29.16 PM
    Tried to add a category to a page, when I did I got this msg after hitting save. Sena@fandom 21:31, February 1, 2011 (UTC)
    • Should now be fixed. Kirkburn (talk) @fandom 15:44, February 11, 2011 (UTC)

Maintenance for Pages Created Using LayoutsEdit

  • Once a user builds a page using a layout, it can then not be edited by conventional means. This is a nightmare, and essentially makes layout builder unusable as is. If a decision has been made to specifically have it work the way it currently does, so that novice users can still add content easily, then there needs to be some way for admins to switch over to the standard editing mode. Otherwise layouts are creating stagnant pages that can never be updated or improved upon cosmetically. —XD1 20:30, March 8, 2011 (UTC)
  • Diff page show meaningless code. This isn't really necessary if none of that code is manageable to an editor. —Scott 21:38, February 1, 2011 (UTC)
    • Indeed - we want to improve it by only showing the changes to the parsed wikitext (i.e. make them more like normal diffs). And, eventually our diffs should be more WYSIWYG in style. Kirkburn (talk) @fandom 15:30, February 11, 2011 (UTC)

User ExperienceEdit

  • At first, I was not keen on the idea of not having the wiki code option available when editing an article created using layouts. However, after some use, I'm starting to see the benefits of hiding that from certain editors. —Scott 21:47, February 1, 2011 (UTC)
    • Randomly related-ish: eventually the inputs on the form should be a form of rich text editor. Kirkburn (talk) @fandom 15:28, February 11, 2011 (UTC)
  • Although it's quite exciting to see a nice implementation of a semantic or field-based content mode for MediaWiki (not quite sure what the right term is) this feature presented a bit of a usability conundrum to me as an experienced Wikipedia/MediaWiki user: I went to slap a simple copyright violation notice at the top of a page formatted with the PLB and I couldn't figure out how to do that easily and was sort of derailed from my mission.
It seems to me that there really ought to be an obvious, intuitive way to transition the page from a PLB-controlled format to a normal wiki markup; there are always going to be use cases requiring this that even a very good engineer can't anticipate.
I am told that right now I would have to delete the PLB-controlled article and create a standard wiki article with the same name in its place. A tool that might be simple to program that could greatly facilitate this would be something like the "View Source" for a protected article or template on Wikipedia: a PHP page (or whatever) that provides a rendering of the PLB-controlled article in standard wiki markup in a read-only text field that the user can cut and paste from. It wouldn't need to be an exact rendering of the article, just enough to prevent you from having to individually cut and paste the contents of every single field in the layout. (Perhaps a warning message could explain that the rendition of PLB to wiki markup code isn't exact, if some technical issue makes this difficult.) --Cumin The Barbarian 03:01, March 10, 2011 (UTC)

Notes for Layout BuildersEdit

  • For the character template, it might be a little confusing to the editor to "enter the file name" for uploading images, since it's a process to upload pictures to your profile/talk page, then take the "File" and copy/paste back to the template. Just a personal note...because I intially didn't know how to do it myself. Kate.moon 20:17, February 1, 2011 (UTC)
    • Aye, tis an interesting use case (since it involves a fragment of the image tag rather than the whole thing). Hmm. Kirkburn (talk) @fandom 15:44, February 11, 2011 (UTC)
http://enttesting.wikia.com/wiki/Page_Layout_Builder_Notes
enttesting.wikia.com
crawl=CC-MAIN-2018-34
180313
application/http; msgtype=response
sha1:T54GBFV4RTLE5A5IWBCX3AUYMXDHQ57I
<urn:uuid:40c9f432-fd8c-4dbf-90c4-eca890ae6445>
2018-08-17T23:11:57Z
151.101.192.194
text/html
sha1:PQUCPCK6SA6A7NA6HOYER3VQRVPKEGIQ
<urn:uuid:f65e0a98-c5f8-4eb3-8927-5ff62d130433>
http://enttesting.wikia.com/wiki/Page_Layout_Builder_Notes
response
<urn:uuid:025f9a47-ac64-4ff2-81f8-80b64b02bf09>
isPartOf: CC-MAIN-2018-34
publisher: Common Crawl
description: Wide crawl of the web for August 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-146-107-43.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/