How to fix 'fatal error'?

claus_01 — Mon, 25 Aug 2008 13:57:48 +0000

Hi Bdesign,

many thanks, it worked! ;-)

Claus

How to fix 'fatal error'?

Bdesign — Mon, 25 Aug 2008 05:04:29 +0000

After you have installed 0.9.3, you have to delete 2 snippets : comment-form and comment-each if I memory is good. Then deactivate the comments, and reactivate them. Don't forget your comments tab has to disappear for the comment plugin to be deactivated. Hope it helps.

How to fix 'fatal error'?

claus_01 — Mon, 25 Aug 2008 01:01:40 +0000

Hi David,

since I had 0.9.2 installed, I upgraded to 0.9.3. Now the German interface is there alright, but I am getting an error message again:

Fatal error: Call to undefined method Page::commentsCount() in /home/www/web266/html/blog/frog/app/frontend/classes/Page.php(330) : eval()'d code on line 1

Both the comments & the sidebar have disappeared. I have copied the layout from the previous installation, and otherwise everything is displayed ok (logo, layout, etc.). Do you probably know how I can fix this?

URL: http://www.ergotherapie-scharnhauserpark.de/blog/

TIA,

Claus

How to fix 'fatal error'?

David — Fri, 22 Aug 2008 03:42:10 +0000

Hi again Claus:

English text in the frontend - If you mean things like "About Us", etc., then you just have to change them by hand, I'm afraid. I don't think there is a standard "translation" pack/technique for the frontend. The exception is dates: you can set up dates to display in the frontend in your own locale settings - you can see some information about this in the Frog docs and see also this forum post (which may just repeat what is in the docs!).

"only options available are 'English' and 'French'." -- Uh oh! What version of Frog are you using? If you check the online demo of 0.9.3, you will see there are i18n options for Bengali (Bangla), Czech, Dutch, French, German, Hungarian, Italian, Japanese, Polish, Russian, and Spanish. :)

Hope that helps! http://www.opensourcecms.com/cms/frog/admin.html

How to fix 'fatal error'?

claus_01 — Fri, 22 Aug 2008 02:40:02 +0000

Hi David,

> translate messages into German: do you mean in the Admin interface?

no; actually, I was referring to the English text in the frontend. Do you probably know where this text is included? I went through the files of frog/apps/frontend, but couldn' t find it.

Besides, I am not able to change the language of the admin interface to 'German', because the only options available are 'English' and 'French'. Dou you know where the respective file(s) for the localization can be found?

TIA,

Claus

How to fix 'fatal error'?

David — Wed, 20 Aug 2008 12:36:14 +0000

Hi Claus - Good news! :)

translate messages into German: do you mean in the Admin interface? You probably mean something else ;) but just in case, you can set the backend language by going to Administration > Settings > Language, and picking "German" from the drop-down menu;
change the name of 'Archives': I guess you could always use "Artikeln" or "Nachrichten", neither of which mean "Beiträge", of course, but you would avoid the problematic (for Frog!) characters. But you knew that already, of course!

How to fix 'fatal error'?

claus_01 — Wed, 20 Aug 2008 11:21:20 +0000

Hi David,

I got it to work by now:

http://www.ergotherapie-scharnhauserpark.de/blog/

All I have to do now is, to translate the messages into German, and to change the name of 'Archives'.

Thanks for your support!

Claus

How to fix 'fatal error'?

David — Tue, 19 Aug 2008 13:18:03 +0000

:) Glad you found the problem!

About "ä" -- this is a known issue and we'd love to have a fix!

How to fix 'fatal error'?

claus_01 — Tue, 19 Aug 2008 13:14:38 +0000

P.S.:

> You can see how to change the name of your "Articles" page in this forum post

Apologies! I overlooked this at first.When I changerd the name back to 'Articles', the error was gone!

Claus

How to fix 'fatal error'?

claus_01 — Tue, 19 Aug 2008 13:03:51 +0000

Corr: "how easy" ;-)

Claus

How to fix 'fatal error'?

claus_01 — Tue, 19 Aug 2008 13:01:24 +0000

Hi David,

thanks a lot! Since this blog is for German readers, is there a way to keep the name of this section (In German: 'Beiträge') while changing the name of the file to 'articles'? Otherwise, I was really surprised hos easyFrog was to install.

Thanks again,

Claus

How to fix 'fatal error'?

David — Tue, 19 Aug 2008 12:48:15 +0000

Hi Claus - I think it is because you have renamed the "Articles" page as "Beiträge" ... or at least, Frog is looking for "Articles" in its foreach loop.

You can see how to change the name of your "Articles" page in this forum post. Also, note that the "slug" of your Beiträge page will be "beitrge" since the "ä" will get dropped out. :( (That's another problem! It is being worked on!). Essentially, you want to repace all occurrences of $this->find('/articles/' to $this->find('/beitrge/'.

I think! I could be wrong. I have been wrong before. ;) Let us know how you get on!

How to fix 'fatal error'?

claus_01 — Tue, 19 Aug 2008 12:00:14 +0000

Hi,

I just installed the latest version of Frog, and in the beginning everything was displayed just fine, but after deletring a few (imho unneccesary) files from the sidebar, I am getting 'Fatal error: Call to a member function children() on a non-object in /home/www/web266/html/blog/frog/app/frontend/classes/Page.php(170) : eval()'d code on line 2'. I performed a complete new install, but the problem is in the database (MySQL). I am logged in as admin (Administration), and I disabled the SQLite 3 plugin. Still, the problem remains. Interestingly, at http://www.ergotherapie-scharnhauserpark.de/blog/?about_us, the error nmessage isn't there; only at http://www.ergotherapie-scharnhauserpark.de/blog

Recent Posts of Frog CMS in How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?

How to fix 'fatal error'?