Warning: No templates specified.

[FL0RIAN]

I always get this error message Warning: No templates specified. after backend login.
Does anyone have a clue?

Thanks for your support.

[bernhard]

no

clear all your unnecessary server and client cache+sessions+cookies etc related to that site and try it again.

[FL0RIAN]

Thanks, but this did not help.

[adrian]

Can you do a Modules > Refresh ?

http://pwtest.test/processwire/module/?reset=1

The error is coming from the ProcessField.module file - it looks like it is trying to send a field to a template so I think there must be something cached there that needs to be cleared.

[FL0RIAN]

Still the same

[FrancisChung]

It's not this error you're referring to right?

You must assign a template to the page before setting custom field values (title__data) [pageClass=Page, template=]

[FL0RIAN]

No, it has to be something different.

[Macrura]

well, it's not an error, it is a warning. You could ignore it (?)

Alternately - did you already enable DEBUG mode, install TracyDebugger?

that warning may be coming from this file:

wire/modules/Process/ProcessField/ProcessField.module

but i don't know why that file would be in play upon login, unless you have a module or some hook somewhere doing something.

[FL0RIAN]

TracyDebugger did the trick. It was the PageListImageLabel module. Thanks Macrura! 

[FrancisChung]

Haha, maybe it's about time I dusted off Tracy Debugger too.

Was an early adopter but have never used it because I was on PW 2.8.x for a long time until recently.

[adrian]

1 minute ago, FrancisChung said:

but have never used it because I was on PW 2.8.x

It should have worked on 2.8. I tested on 2.7 early on, but now restrict testing to 3.x, but I don't really know why it wouldn't have worked on 2.8 - did you get errors?

[FrancisChung]

I'm pretty sure I read somewhere in the beginning that PW 2.x was not officially supported, at least in the very early versions, which is why I just got the early bird deal and never used it.

Perhaps that has changed over recent iterations?

 

Just now, adrian said:

It should have worked on 2.8. I tested on 2.7 early on, but now restrict testing to 3.x, but I don't really know why it wouldn't have worked on 2.8 - did you get errors?

 

[adrian]

I think there were a couple of really early 2.x bugs and one panel that didn't work, but I think that was it.

Anyway, you have moved on now, so no need to worry