Please help me, i become this message, when i want to chance my templates since today, but i'm not sure what i have done?

The Version of XOOPS is 2.0.5.1 and have change the server a few days ago. Then i got the "Virtual Host"-Problem and become allways the message "Selected Module does not exist" an found this thread in this forum...where Ender solved my problem. But now, i can not change the templates - i'm very confused

migoe

Is there no man who knows this problem?

migoe

Update your modules in the system admin -> modules pags, this will re-insert all templates into the database.

Herko

Hi Herko,

thanks for your help, but theres no effect if i done this

Hi there, I have this problem too. Just appeared out-of-the-blue on one of my sites.

Specifically: After 8 months of smooth running, we got hacked. As far as I can see, the hacker only took out the index.php and put on a dumb index.html.

After replacing the index, the problem appeared.

We noticed that a particular block on the front page of the site is blank - odd... especially since turning on php or smarty debug shows no errors. So, is it a problem with templates? All the other templates (both in this module and in other modules) appear fine.

So, I think: "this must be a bug in the block." Without direction from page errors; I go to the template manager. Here's the real problem:

I can navigate into the templates/module listing for any of my template sets, but when I select an individual template file to edit (again, from any of the template sets), I get the error referred to by migoe:

Selected template (ID: $id) does not exist

I have no clue what's going on; any leads you can offer would be great.

Thanks,
Keith

Don't know if it will work - try upload that particular template and let system regenerate the template hopefully with a correct ID.

Thanks tl, a version of this solution worked:

Report:

- all template sets seemed to have messed up ids
- templates still showed properly on the page
- I cloned my active template set, and set the cloned set as primary
- the cloned template set worked properly on the template MGR