search

obdev / WebYep

Web Content Management System
20 stars 13 forks source link

WebYep and Mavericks OS X 10.9 #1

Open skaicaptain opened 11 years ago

skaicaptain commented 11 years ago

I seem to be having a problem with the webyep plugin and mavericks (os x 10.9 gm). I get this error message in one project when trying to publish via ftp or local:

Exception while exporting site -[__NSCFString appendString:]: nil argument

theme is CASphere1, but changing to a different theme does not help.

it happens only on webyep (plug-in) pages :( any idea what is going wrong? there is no webyep support anymore from Objective Development :(

the webyep stacks from tsooj in a stacks page work fine!

thanks a lot! kai

obdev commented 11 years ago

We at obdev currently don't have the resources to track this down. When the problem occurs, it should be relatively easy to attach a debugger and track it down. If somebody has a fix, we'd be happy to pull it.

skaicaptain commented 11 years ago

thanks for your reply! "attach a debugger" sounds cool to a layman, but I can't do it. I hope someone can and will. thanks again!

skaicaptain commented 11 years ago

I need to add something important: newly created webyep (1.7.3) pages do not show this error! but already created pages (also with 1.7.3) in existing projects show this error. in-depended from the theme used - as far as I can tell. maybe this helps to find a solution.

MiDoe commented 11 years ago

just came across the same issue

skaicaptain commented 11 years ago

I knew I would not stay alone... I still have no solution besides adding new webyep pages to the project file and deleting the old ones :( have not figured out how to keep the content, though. keeping the same file name and path does not do the trick. any ideas?

skaicaptain commented 10 years ago

SOLUTION AHEAD

I don't know right now if I should cry or rejoice. this is crazy!

I just found - after pondering the whole issue under new the circumstances again - the reason for the whole problem.

I started rapidweaver by default in english language for quite a while. I must have switched to english around the same time I switched to mavericks. I did this because I ran in to another problem with a stack and german "umlaute". switching rapidweavers language to english solved that problem but created this webyep problem on the way. grrrrrrrrrrrrrrrrrrrrrrr!!!!!

now after a small brainwave I started rapidweaver in german again.

no

more

problems....

so only german rapidweaver with german or (!) englisch webyep. but no english rapidweaver with german webyep (but with english webyep of course)

one problem less to solve here :)

MiDoe commented 10 years ago

I switched the fieldname language from english to german, which made the trick for me.

So it seems that fieldname language should go along with RapidWeaver Language setting.