Thus duplicate produces a row of Apache and PHP errors. I was able to deploy it only with several manual adjustments.
This is strange, usually, the Duplicators work fine if they also completed properly on the origin site.
The errors seem mainly related to missing database tables, but also several PHP 7.x compatibility issues right upon the site start (Toolset Types fixed those here: https://toolset.com/errata/php-7-3-shows-warnings-about-continue-statement-in-types/)
I see those PHP errors affect mainly these plugins:
revslider, duplicator (wow, who would have thought this)
In any case, I was able to deploy the site finally and on the homepage, I found another (additional to above) error:
Warning: preg_match(): Compilation failed: invalid range in character class at offset 12 in /js_composer_theme/include/classes/shortcodes/vc-basic-grid.php on line 184
Removing all plugins (deactivating) unless Toolset resolved all issues unless the one on add-event/ page you reported here.
I also removed the "must use" plugin, cleaned the .htaccess and wp-config.php, which did not solve this problem either.
Even disabling the theme did not solve this issue.
The code affected here, cred-frontend-editor/application/models/form/relationship.php line 415, says:
$field[ 'data' ][ 'post_type' ] = $field[ 'data' ][ 'post_reference_type' ];
Hence, it fails on $field[ 'data' ][ 'post_reference_type' ]; assuming [ 'post_reference_type' ] to be an unexisting index of $field['data'] and that code is explicitely used for post reference fields. But there are no such fields in that form.
Only relationships, no post references.
The data index has an array of values:
["data"]=> array(10) {
["slug-pre-save"]=> string(11) "event-venue"
["placeholder"]=> string(0) ""
["user_default_value"]=> string(0) ""
["repetitive"]=> string(1) "0"
["custom_use"]=> string(0) ""
["conditional_display"]=> array(0) { }
["submit-key"]=> string(11) "event-venue"
["disabled_by_type"]=> int(0)
["validate"]=> array(0) {
}
["post_type"]=> NULL
}
[ 'post_reference_type' ] is not there.
The data on your site tells me that this should be the field "event-venue", that is not a PRF but a simple single line, and that is the reason, there is no [ 'post_reference_type' ]
And I believe I found what is the reason for the form assuming it is a PRF field...
You also have a Relationship with the exact same slug!
In fact, as soon you rename the Custom Field event-venue to event-venue-anything-new the issue is resolved.
Now, I am quite sure this is replicable, and probably expected as you should rarely use the same slug for 2 things on a site, but then, it's surely not OK for Toolset forms to assume a PRF just because you happen to have a field with the same slug as a relationship on your site.
I am escalating this and will try a clean reproduction tomorrow, and a fix if needed.
Meanwhile, you could rename that field - but be aware that renaming it, also will, of course, change the way you have to display already saved data, so maybe you better wait until I have a proper solution or precise statement from the DEV about this.
