VZ URL extension
ExpressionEngine 1.x, ExpressionEngine 2, ExpressionEngine 3
Back to this add-on's main page
View Other Add-ons From Eli Van Zoeren
PHP Error
Support Request
Joobs
|
Posted: 04 July 2011 10:16 PM |
|
|
|
Just been updating my site and i get this error when i go to the fieldtype settings page.
A PHP Error was encountered
Severity: Warning
Message: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'Vz_url_ft::display_global_settings' was given
Filename: api/Api_channel_fields.php
Line Number: 350
EE2 v2.2.1 - Build: date 20110630
VZ URL: 1.2.1
|
|
|
Eli Van Zoeren
|
Posted: 05 July 2011 02:46 PM |
# 1
|
|
Developer
|
Hi Joobs,
There is actually no longer a settings page for VZ URL (its only function was to change error message wording, which is better handled in the language file). Unfortunately, EE doesn’t register that change until the fieldtype is disabled and re-enabled. If you do that, the link to the settings page will go away, but so will any URL fields you have set up in your channels. So, honestly, I would just recommend that you ignore that settings link. Hopefully an “update_fieldtype” hook will eventually be added, as there is for extensions, so I can make that change in the database when you upload a new version of VZ URL.
Sorry, I know that’s not ideal but I don’t see any other practical solution at this point.
|
|
|
Joobs
|
Posted: 05 July 2011 03:20 PM |
# 2
|
|
|
thanks for the reply.
If i disable the fieldtype, do those existing fields turn into text inputs or something? And then could i reassign them?
|
|
|
Eli Van Zoeren
|
Posted: 05 July 2011 03:21 PM |
# 3
|
|
Developer
|
No, that’s the way it working in EE 1.6. But for some incomprehensible reason, in EE2, when you disable a fieldtype, it deletes all the fields of that type and all their data. I believe there was a bug report filed for that at one point, but I’m not sure what ever happened with it. I suppose you could manually change all the VZ URL fields to text fields (which shouldn’t touch the data, I don’t think), disable and re-enable VZ URL, and then change the field types back.
|
|
|