1
numbat2
Fatal error going to 2.0.10
  • 2005/5/30 9:35

  • numbat2

  • Just popping in

  • Posts: 6

  • Since: 2004/4/25


I updated from 2.07 to 2.0.9.2. Seemed to all be fine.

I then stepped up to 2.0.10 and had a few odd things creep in. The footer still reads as version 2.0.9.2 even though I have uploaded the update to 2.0.10 twice.

More bothersome is this error when I try to go some pages.

<input type="hidden" name="XOOPS_TOKEN_REQUEST" value="
Fatal error: Call to a member function on a non-object in /home/numbat2/public_html/templates_c/%%5A^5A2^5A255BBF%%db%3Asystem_notification_select.html.php on line 12
Notice [PHP]: Constant _MI_TEXT already defined in file modules/xoopspartners/language/english/modinfo.php line 38
Notice [PHP]: Use of undefined constant _XT_TE_BLOCO - assumed '_XT_TE_BLOCO' in file modules/xt_temas/blocks/xt_temas.php line 6

Any tips would be appreaciated.
Numbat

2
jdseymour
Re: Fatal error going to 2.0.10

Have you updated the system module in System Admin - Modules?

3
numbat2
Re: Fatal error going to 2.0.10
  • 2005/5/30 10:16

  • numbat2

  • Just popping in

  • Posts: 6

  • Since: 2004/4/25


I have updated all the modules by clicking on the update icon on the right of the admin page.

I also deleted everything from the templates_c folder and updated again.

4
jdseymour
Re: Fatal error going to 2.0.10

Try to re-upload the files, maybe something did not transfer completely.

5
numbat2
Re: Fatal error going to 2.0.10
  • 2005/5/30 10:45

  • numbat2

  • Just popping in

  • Posts: 6

  • Since: 2004/4/25


I'll try stepping back to 2.0.9.2 then update to 2.0.10 again if it all looks ok.

6
numbat2
Re: Fatal error going to 2.0.10
  • 2005/5/30 11:33

  • numbat2

  • Just popping in

  • Posts: 6

  • Since: 2004/4/25


Quote:

numbat2 wrote:
I'll try stepping back to 2.0.9.2 then update to 2.0.10 again if it all looks ok.

Yep. That seemed to work. That's a relief.
Numbat