This question about Configuration: Asked
special pages view is messed up
Hello,
I just installed AutoTemplatePlugin and it perfectly does what it's supposed to do. Thanks very much for the suggestion. It's great.
Now, the only problem I have is with the special pages (like template=oopshistory, template=more, and so on). All of them were working properly before installation, but now, they always display elements from my normal View-Template that were not displayed before (mostly the websidebar), and they overlap the contents, what makes clicking on it impossible. I have no idea what I might have done wrong. Maybe my View template is not configured correctly, but it did work correctly before installation.
My current configure settings are as follows:
- AutoViewTemplatePlugin is not enabled
- AutoTemplatePlugin is enabled
- override is "enabled"
- Mode is "exist"
Is there anything I need to change in the WebPreferences maybe?
--
Lieven - 31 Aug 2021
Try disabling override.
--
MichaelDaum - 31 Aug 2021
I have tried that, it does not make any difference.
What confuses me is that this does not affect all all pages. It seems to depend on the use of forms and the existence of their counterpart Templates.
Example:
This page uses the "!UserForm" and there is no "!UserViewTemplate" (the template is definied in the "more settings" of the page); the layout is distorted:
This page uses the "!TopicForm", and there
exists a "!TopicViewTemplate", but the layout is distorted:
This page uses the form "!Word_1_definitionForm" and there
exists a "!Word_1_definitionViewTemplate"; the layout is distorted:
If the page uses NO Form then the layout works fine:
Maybe it helps if I tell you which actions are affected:
- works fine: edit, print, raw,
- does not: attach, history, backlinks, more, rename
I believe there is no fault in the extension; I begin to wonder if there is something wrong with my templates. The question is why and where? It did work before I started the plugin.
--
Lieven - 31 Aug 2021
Hm,
http://klingon.wiki/bin/oops/Main/LieVen?template=oopshistory looks just fine to me ...
--
MichaelDaum - 31 Aug 2021
Now it does, indeed. I suppose that the website needed some time to realize that there was a change in the settings. I'm not sure why or how, but I guess it was the solution to disable the "override".
I wrote the above line this morning, but too quickly. The problem is not yet solved. I tried a few things, and noticed the following:
- When my Webpreferences set a template like
VIEW_TEMPLATE = Word.TopicView
then the backstage pages look fine, but my topics are not displayed using the correct form; Very likely because "override" is disabled.
- When I deactivate that setting for the view template, then the form-connected templates work fine, but then the backstage pages are messed up.
So my question still exists. PLEEEEASE HELP!
--
Lieven - 01 Sep 2021
Try to eliminate any VIEW_TEMPLATE settings in
WebPreferences,
SitePreferencces or the topic itself. Revert the
AutoTemplatePlugin settings to their defaults.
Test with ?template=view to eliminate any preference setting whatsoever. In any case will a template url parameter take highest precedence. Check your SKIN settings and how it affects the
view
template. Try to reset the SKIN to
pattern
. Disable any setting of COVER. See if the problem still persists.
Make use of auto-templating: given a form
FooBarForm, create a
FooBarViewTemplate in the same web that the form is in; it will be used automatically.
--
MichaelDaum - 01 Sep 2021