Jump to content

Template editor and field editor not showing anything [Solved]


Joss
 Share

Recommended Posts

UPDATE - Installing the dev from today seems to have solved the issue

On the sites I have upgraded to 175, when I click on Setup->Templates->Template name, I just get nothing as shown in the pic below.  Well, it says I am editing it, but there is nothing shown even though the pages are working fine.

The same happens when I click to edit a field

This is happening on both dev sites on my local set up and on live sites. When I updated (from 168, I think), I also updated a pile of other things like ListerPro, page actions, a couple of pro fields. Not that I think they are anything to do with it, but I throw them into the mix in case.

It is the same in the Ukit and default themes, so it's not a theme issue.

Any clues? Have I missed an important announcement somewhere?

I was about to start on a new site, and I can't!

Joss

empty-template.thumb.jpg.fa87ea0fd525efc17e823735d1fcedd4.jpg

 

Link to comment
Share on other sites

I'm running 3.0.175 on a dev site and all works as expected for editing admin templates & fields.

Have you tried reverting to the PW default UiKit admin theme? Maybe something to do with the custom admin theme you're using

Link to comment
Share on other sites

Hi, psy

It's the same on all themes. I have just noticed this in the Chrome console. No idea if it has anything to do with it, but I am not getting it on sites without the problem:

Uncaught SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at HTMLDivElement.<anonymous> (InputfieldTextTags.min.js?v=1-1619298240:1)
    at Function.each (JqueryCore.js?v=183:2)
    at init.each (JqueryCore.js?v=183:2)
    at InputfieldTextTags (InputfieldTextTags.min.js?v=1-1619298240:1)
    at HTMLDocument.<anonymous> (InputfieldTextTags.min.js?v=1-1619298240:1)
    at l (JqueryCore.js?v=183:2)
    at Object.fireWith [as resolveWith] (JqueryCore.js?v=183:2)
    at Function.ready (JqueryCore.js?v=183:2)
    at HTMLDocument.A (JqueryCore.js?v=183:2)

 

Link to comment
Share on other sites

A little bit more. Looking at the page source, the following form is not showing:

<form id="ProcessTemplateEdit" class="InputfieldForm _InputfieldWrapper3" method="post" action="save" data-colspacing="0">

The css is:

.pw-init #ProcessTemplateEdit {
    display: none;
}

If I delete "none" in Chrome console, the page shows.

Link to comment
Share on other sites

18 minutes ago, Joss said:

I have just noticed this in the Chrome console. No idea if it has anything to do with it, but I am not getting it on sites without the problem

You should also be able to see the Ajax request and the returned data that causes that error in the dev console. This should give you more of a clue, as the error reads like the returned data isn't JSON at all. It's probably an error or warning from PHP that JS tries to parse.

Link to comment
Share on other sites

4 minutes ago, BitPoet said:

You should also be able to see the Ajax request and the returned data that causes that error in the dev console. This should give you more of a clue, as the error reads like the returned data isn't JSON at all. It's probably an error or warning from PHP that JS tries to parse.

This is where my abilties crash! But here is a screenshot:

ajax-request.thumb.jpg.fdeac7dd6b0ec68ae3371c80b82c6b5a.jpg

Link to comment
Share on other sites

For some reason, it is taking it's css from ProcessTemplateEdit id (which is in the ProcessTemplate.css file in the core), rather than from the admin theme class ProcessTemplateEdit. 

Link to comment
Share on other sites

7 minutes ago, cb2004 said:

Ryan made some updates last night which fixed it for me. Have you tried the latest dev?

Ah, I thought I was on the latest. I will go check

Link to comment
Share on other sites

15 minutes ago, cb2004 said:

Ryan made some updates last night which fixed it for me. Have you tried the latest dev?

Okay, I have just overwritten Wire from the one from the DEV download and that seems to have solved it. The version is still showing as 175.

Link to comment
Share on other sites

39 minutes ago, cb2004 said:

Yes he hasn't bumped the version to 3.0.176 yet. Some things do break here and there on the dev branch but its very rare.

I don't think I have had that kind of problem in the last nine years! Which says a lot for Ryan.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...