Difference between revisions of "If your story doesn’t show up on the Dashboard"

From MTG Wiki
Jump to: navigation, search
Line 8: Line 8:
  
 
<h2>Important Notes:</h2>
 
<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.
 
* 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.
 
* 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.

Revision as of 14:37, 24 January 2019

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

Check the following to make sure the story gets processed by the system:

Important Notes:

  • 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.