HIPO's messing with my Easy Edit Suite

(Ryan Archer) #1

Hi all,

 

First time setting up Easy Edit Suite (EES) on a website using Squiz Matrix 4.18.4 and I have a HIPO in the room (obviosuly that is tongue in cheek idiom). But I have followed the manual to the letter to setup an Easy Edit on the website we have built and it keeps throwing a HIPO error saying:

 

A HIPO job with this code name is currently run by "some guys name" (ID: #123456). Last updated at 10/04/2015 14:36:08 [HIPO004]

 

Actually the first time I try mywebsite.com.au/_edit it just shows the Squiz Matrix backend with a blank screen, I wait for a while and then I try and login again and get thrown the error above. Obviously it is telling me that I can't be logged in twice as the first operation (of logging in) has not been completed. Is there anything I can do or troubleshoot to solve this issue?

(Joel Porgand) #2

fire up the HIPO herder and delete or resume the job in question

 

if it keeps happening then you'll need to troubleshoot further as to why the jobs are failing

(Ryan Archer) #3

I've tidied up some of the references but I still can't get the EES login screen to appear no matter what I do. It just shows a blank screen and obviously leaves a HIPO open ended until I delete the job and test it again.

I followed the instructions here at https://manuals.matrix.squizsuite.net/ees/chapters/installation#Changing-Global-Preferencesto the 'letter' and still having grief....

(Tim Davison) #4

Does the matrix admin interface bar come up along the top?  If so you need to make sure the site design is set to no frames for simple edit interface.  If you miss this a HIPO will be created (and get stuck) every time EES tries to get locks (aka every time you open it).

(Ryan Archer) #5

Thanks but that wasn't the issue was. I am not really sure what it was really. Just one of those moments where you need to give it up and come back to it again. I suspect it was because my home page customisation lost the nested content for EES - not really sure how it did it but it sometimes happens so I have to remember to always double check ALL nested content when editing a customisation.

 

I have noticed other weird anomlies that have appeared and then disappeared within 24 hours with no apparent explanation rather than a generic 'oh that must have been a cache issue' explanation... 

(Anthony Ponomarenko) #6

Just a tip. You can append /_nocache to a URL to serve an uncached version.

(Ryan Archer) #7

Thanks Anthony. I know about that one. Still did not make a difference in this instance.