ga-uk

Thank you for your rapid response.

This is a great plugin. I look forward to when the bug is fixed as that would make it nearly perfect!

Ok…

So, much testing and the problem comes down to something very simple.

CFT has some reserved words that cannot be used as field names.

For example if you use the field name [type] updating posts/pages using that cft will give the php warning.

I don’t know how many reserved words there are but it might be safe to assume that all ‘option’ words, e.g. “type =” are reserved.

I hope this info saves someone some time…..

Some more information –

I’ve downloaded WordPress move 1.3 from a live site where it installs and works well.

I’ve installed it on a site on my localhost (Nginx 1.1.7, PHP 5.3.8 WP 3.3.1) and I get the fatal error warning when activated. As previously wp-debug on, provides no further information.

Just hope that the problem is fixable one way or another!

Thank you.

BTW I’m running localhost on windows install of Nginx 1.1.7

Don’t think it’d make any difference but thought I’d mention it just in case!

I also have the fatal error on activation issue using wp-move version 1.3.

I’m trying to use the plugin on a development site on localhost.

I’m using WordPress 3.3.1 and php 5.3.8. I’ve deactivated all other plugins.

I’ve turned on wp-debug but I get no further information.

Any ideas?

Thanks

Fast work!

Thank you.

Thanks t31os_ that is a good approach – I was just too inexperienced to see it. I think I’ll be able to fix it now using a counter.

Regards.