[SOLVED} Blog module - Truetype-Directory is not readable!

[turniphead]

After installing the Blog module, I get the error "Truetype-Directory is not readable!" on trying to view an individual post. Any ideas what it might be? I installed the truetype module but that didn't help.

[turniphead]

Anybody? I've grepped the error message in the cmsmadesimple directory and not gotten a result, so I'm kinda stuck.

[solotwin1]

I've had the same problem, except with SelfRegistration and FrontEndUsers. I used the nocaptcha="1" parameter and I was immediately able to use the modules. I think the problem is with the Captcha module, so if you have Captcha installed, I recommend that you uninstall it and see how it goes from there.

[turniphead]

Sorry - I solved the problem a week after my last post and forgot to posty the solution. As you say, it was the captcha module. I changed a parameter which selected how to render the captcha and that fixed the issue.

[rvaneerd]

Hi there,

I ran into the same problem, however in my situation, it was the FormBuilder module (that is, displaying a form build with FormBuilder).
After reading the posts in this topic, I Solved it by de-installing (and removing) the Captcha module and then re-installing it again (as I need the Captcha module and didn't know where to check for the "parameter to change the rendering").

Regards,
Rob van Eerd

[Dr.CSS]

What is most likely happening is you install captcha with Mod. Mana. and it gets permissions that don't let it work, then you uninstall it and instaill in extensions > modules and it gets the correct permissions, if you have this problem FTP to site to see the perm. on it then do the uninstall/install routine then FTP to site again to see the permissions have changed...

[acuitas]

Mark

God bless you for this fix. I just transferred my entire website to a new server, and this problem surfaced. I was completely stumped. It screwed up several pages with forms on them linked to the data base. I thought I was screwed. I read this and in two clicks, the problem was gone. Thank you!

[ESBertrand]

Simply uninstalling and reinstalling the module (through the admin) fixed the problem for me, too.  I didn't even have to remove any files or change any permissions or anything.  I bet the module stores the root path somewhere in its cache, or in the database.  We had moved our site from one host to another as well, which explains the problem.

Erik

[Dr.CSS]

Just to let everyone know, Yes captcha does store some information in the DB so moving a site will make it not work, the simple uninstall/install fixes these problems...

[kerryshamblin]

Thanks! This saved me time. I love this forum.

[replytomk3]

I was just about pulling my hair - same message, whole site down after move to another directory. Turns out it was CGFeedback. Start by commenting out any module calls in the template and see what gives you the problem.