MTG Wiki - User contributions [en]

MTG Wiki Test Page Prod

2022-12-14T09:49:28Z

Mylene:

<h2>This is the headline</h2>

This is a TEST by MyS for validation purposes only. Kindly disregard.

Porttitor lacus luctus accumsan tortor posuere ac ut. Risus quis varius quam quisque id diam vel. Lectus sit amet est placerat in egestas. Lobortis elementum nibh tellus molestie nunc.

----

[[File:Dummy.gif]]

MTG Wiki Test Page Prod

2022-12-14T09:49:14Z

Mylene:

<h2>MTG Wiki Test Page Prod</h2>

This is a TEST by MyS for validation purposes only. Kindly disregard.

Porttitor lacus luctus accumsan tortor posuere ac ut. Risus quis varius quam quisque id diam vel. Lectus sit amet est placerat in egestas. Lobortis elementum nibh tellus molestie nunc.

----

[[File:Dummy.gif]]

MTG Wiki Test Page Prod

2022-12-14T09:23:58Z

Mylene:

File:TechArticle1.png

2022-12-14T09:23:47Z

Mylene:

MTG Wiki Test Page Prod

2022-12-14T09:08:51Z

Mylene: Created page with "<h2>MTG Wiki Test Page Prod</h2> This is a TEST by MyS for validation purposes only. Kindly disregard. Porttitor lacus luctus accumsan tortor posuere ac ut. Risus quis vari..."

Another Test Page

2022-12-12T17:07:02Z

Mylene: Created page with "<h2>Another Test Page </h2> This is a TEST page created in the MTG Wiki for validation purposes only by MyS. Kindly disregard. File:Pumpkin_gnocchi_with_Idahoan_sponsored.j..."

<h2>Another Test Page </h2>
This is a TEST page created in the MTG Wiki for validation purposes only by MyS. Kindly disregard.

[[File:Pumpkin_gnocchi_with_Idahoan_sponsored.jpg]]

File:Pumpkin gnocchi with Idahoan sponsored.jpg

2022-12-12T17:06:20Z

Mylene:

Adding an issue

2022-12-12T17:04:03Z

Mylene:

To ensure that an issue shows up in the archive (http://plateonline.com/issue-archive) upon publishing, we need to ensure the following fields are filled out.

* [[Title of the issue]]
* [[Body copy of the issue]]
* [[Issue Date for Archive]]. This includes the months the issue covers and the year. Have it written as i.e. May/June 2018
* [[Issue sorting date]]. Consists of the month the issue is launched and the year. Have it written as i.e. May, 2018
* [[Issue cover]] with dimension of 221x265 pixels

<h2>Adding the flipbook URL to [[magazine cover]]</h2>
* Go to http://library.plateonline.com/archive/?p1=20602
* Click the designated digital edition of the issue and [[copy the url]]
* Go to Drupal dashboard, [[search the name of the issue]] and click 'Edit'.
* Locate the [[flipbook URL field]] and paste the copied URL.
* Hit 'Save'.

Adding an issue

2022-12-12T17:03:17Z

Mylene:

Adding an issue

2019-02-05T23:22:37Z

Mylene:

Magazine cover

2019-02-05T23:22:30Z

Mylene: Created page with "File:Magazine cover flipbook url.png"

[[File:Magazine cover flipbook url.png]]

File:Magazine cover flipbook url.png

2019-02-05T23:22:15Z

Mylene:

MediaWiki:Sidebar

2019-02-05T23:14:36Z

Mylene:

Adding an issue

2019-02-05T23:13:06Z

Mylene:

To ensure that an issue shows up in the archive (http://plateonline.com/issue-archive) upon publishing, we need to ensure the following fields are filled out.

* [[Title of the issue]]
* [[Body copy of the issue]]
* [[Issue Date for Archive]]. This includes the months the issue covers and the year. Have it written as i.e. May/June 2018
* [[Issue sorting date]]. Consists of the month the issue is launched and the year. Have it written as i.e. May, 2018
* [[Issue cover]] with dimension of 221x265 pixels

<h2>Adding the flipbook URL to magazine</h2>
* Go to http://library.plateonline.com/archive/?p1=20602
* Click the designated digital edition of the issue and [[copy the url]]
* Go to Drupal dashboard, [[search the name of the issue]] and click 'Edit'.
* Locate the [[flipbook URL field]] and paste the copied URL.
* Hit 'Save'.

File:Flipbook url pol.png

2019-02-05T23:10:42Z

Mylene: Mylene uploaded a new version of File:Flipbook url pol.png

Search the name of the issue

2019-02-05T23:05:30Z

Mylene: Created page with "File:Issue name drupal.png"

[[File:Issue name drupal.png]]

File:Issue name drupal.png

2019-02-05T23:04:28Z

Mylene:

Copy the url

2019-02-05T23:02:08Z

Mylene: Created page with "File:Digital edition url.png"

[[File:Digital edition url.png]]

File:Digital edition url.png

2019-02-05T23:01:22Z

Mylene:

Flipbook URL field

2019-02-05T22:56:00Z

Mylene: Created page with "File:Flipbook url pol.png"

[[File:Flipbook url pol.png]]

File:Flipbook url pol.png

2019-02-05T22:55:06Z

Mylene:

Adding an issue

2019-02-05T22:51:35Z

Mylene:

Issue cover

2019-02-05T22:48:20Z

Mylene: Created page with "File:Issue cover pol.png"

[[File:Issue cover pol.png]]

File:Issue cover pol.png

2019-02-05T22:48:04Z

Mylene:

Issue sorting date

2019-02-05T22:46:07Z

Mylene: Created page with "File:Issue sorting date.png"

[[File:Issue sorting date.png]]

File:Issue sorting date.png

2019-02-05T22:45:52Z

Mylene:

Title of the issue

2019-02-05T22:40:24Z

Mylene: Created page with "File:Issue Title.png"

[[File:Issue Title.png]]

Adding an issue

2019-02-05T22:39:45Z

Mylene: Created page with "To ensure that an issue shows up in the archive (http://plateonline.com/issue-archive) upon publishing, we need to ensure the following fields are filled out. * Title of th..."

Issue Date for Archive

2019-02-05T22:39:43Z

Mylene: Created page with "File:Issue date of the archive.png"

[[File:Issue date of the archive.png]]

File:Issue date of the archive.png

2019-02-05T22:39:29Z

Mylene:

Body copy of the issue

2019-02-05T22:38:12Z

Mylene: Created page with "File:Pol-issue-body-copy.png"

[[File:Pol-issue-body-copy.png]]

File:Pol-issue-body-copy.png

2019-02-05T22:37:49Z

Mylene:

File:Issue-body-copy.png

2019-02-05T22:26:18Z

Mylene:

Issue Title

2019-02-05T22:25:09Z

Mylene: Created page with "File:Issue Title.png"

[[File:Issue Title.png]]

File:Issue Title.png

2019-02-05T22:24:38Z

Mylene:

If your story doesn’t show up on the Dashboard

2019-01-24T14:39:16Z

Mylene:

'''Problem''': Stories not showing up in '''Dashboard''': http://dashboard01.mtgplace.com/

'''Check the following to make sure the story gets processed by the system:'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Make sure that all author fields are filled out as well: '''[[POL author fields]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]''' If not, republish the story in question.
* System processes the data every 2am CST. After doing the above, expect to see the stories the next day.

<h2>Important Notes:</h2>
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
* Same thing with — when the new items were added to the jsonfeed due to the modifications to the view, it was likely pushed off of the list. And if it was pushed off of the list, it would not have been re-processed because the way our software works is that, if the date modified is older than the last modified item in the database it ignores it.

If your story doesn’t show up on the Dashboard

2019-01-24T14:39:01Z

Mylene:

'''Problem''': Stories not showing up in '''Dashboard''': http://dashboard01.mtgplace.com/

'''Check the following to make sure the story gets processed by the system:'''
* Make sure that all author fields are filled out as well: '''[[POL author fields]]'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]''' If not, republish the story in question.
* System processes the data every 2am CST. After doing the above, expect to see the stories the next day.

<h2>Important Notes:</h2>
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
* Same thing with — when the new items were added to the jsonfeed due to the modifications to the view, it was likely pushed off of the list. And if it was pushed off of the list, it would not have been re-processed because the way our software works is that, if the date modified is older than the last modified item in the database it ignores it.

If your story doesn’t show up on the Dashboard

2019-01-24T14:38:28Z

Mylene:

'''Problem''': Stories not showing up in '''Dashboard''': http://dashboard01.mtgplace.com/

'''Check the following to make sure the story gets processed by the system:'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]''' If not, republish the story in question.
* Make sure that all author fields are filled out as well: '''[[POL author fields]]'''
* System processes the data every 2am CST. After doing the above, expect to see the stories the next day.

<h2>Important Notes:</h2>
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
* Same thing with — when the new items were added to the jsonfeed due to the modifications to the view, it was likely pushed off of the list. And if it was pushed off of the list, it would not have been re-processed because the way our software works is that, if the date modified is older than the last modified item in the database it ignores it.

If your story doesn’t show up on the Dashboard

2019-01-24T14:37:44Z

Mylene:

'''Problem''': Stories not showing up in '''Dashboard''': http://dashboard01.mtgplace.com/

'''Check the following to make sure the story gets processed by the system:'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]''' If not, republish the story in question. Make sure that all author fields are filled out as well: '''[[POL author fields]]'''
* System processes the data every 2am CST. After doing the above, expect to see the stories the next day.

<h2>Important Notes:</h2>
* Make sure that all author fields are filled out as well: POL author fields
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
* Same thing with — when the new items were added to the jsonfeed due to the modifications to the view, it was likely pushed off of the list. And if it was pushed off of the list, it would not have been re-processed because the way our software works is that, if the date modified is older than the last modified item in the database it ignores it.

If your story doesn’t show up on the Dashboard

2019-01-23T22:06:55Z

Mylene:

'''Problem''': Stories not showing up in '''Dashboard''': http://dashboard01.mtgplace.com/

'''Check the following to make sure the story gets processed by the system:'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]''' If not, republish the story in question. Make sure that all author fields are filled out as well: '''[[POL author fields]]'''
* System processes the data every 2am CST. After doing the above, expect to see the stories the next day.

<h2>Important Notes:</h2>
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
* Same thing with — when the new items were added to the jsonfeed due to the modifications to the view, it was likely pushed off of the list. And if it was pushed off of the list, it would not have been re-processed because the way our software works is that, if the date modified is older than the last modified item in the database it ignores it.

POL author fields

2019-01-23T22:04:51Z

Mylene: Created page with "File:Author-field-1.png File:Author-field-2.png"

[[File:Author-field-1.png]]

[[File:Author-field-2.png]]

File:Author-field-2.png

2019-01-23T22:04:37Z

Mylene:

File:Author-field-1.png

2019-01-23T22:04:12Z

Mylene:

If your story doesn’t show up on the Dashboard

2019-01-23T21:57:27Z

Mylene:

If your story doesn’t show up on the Dashboard

2019-01-23T21:50:32Z

Mylene:

'''Problem''': Stories not showing up in Dashboard

'''Check the following to make sure the story gets processed by the system:'''
* Make sure the author of the story is registered to the site and is verified. Here's how to do it >> '''[[Adding new authors on PlateOnline]]'''
* Author should have GUID records in Intranet. Here's a reference >> '''[[GUID record sample]]'''
* Check to see if the story is showing up in the jsonfeed: http://plateonline.com/jsonfeed Here's a sample>> '''[[Json feed sample]]'''
* In order for the node processor to work properly in cases when nodes (story, recipe) were not present, the software needs to see that the nodes it's adding has been modified AFTER the last node recorded in the Intranet.
**Republish the story in question
**Make sure that all author fields are filled out.

Json feed sample

2019-01-23T21:49:50Z

Mylene: Created page with "File:Json-feed-sample-01.png"

[[File:Json-feed-sample-01.png]]

File:Json-feed-sample-01.png

2019-01-23T21:49:34Z

Mylene:

GUID record sample

2019-01-23T21:45:00Z

Mylene: Created page with "File:GUID-record-sample.png"

[[File:GUID-record-sample.png]]

File:GUID-record-sample.png

2019-01-23T21:44:39Z

Mylene:

MediaWiki:Sidebar

2019-01-23T21:06:12Z

Mylene: