Symphony.

Since I started using 2.3 I have been plagued by errors when building sections. This is the error I get:

Symphony Fatal Error: Could not find Field at /field..php. If it was provided by an Extension, ensure that it is installed, and enabled.

An error occurred in /var/www/vhosts/intacore.com/subdomains/djb/httpdocs/symphony/lib/toolkit/class.fieldmanager.php around line 524

519             if(!isset(self::$_pool[$type])){
520                 $classname = self::__getClassName($type);
521                 $path = self::__getDriverPath($type);
522
523                 if(!file_exists($path)){
524                     throw new Exception(
525                         __('Could not find Field %1$s at %2$s.', array('<code>' . $type . '</code>', '<code>' . $path . '</code>'))
526                         . ' ' . __('If it was provided by an Extension, ensure that it is installed, and enabled.')
527                     );
528                 }

Strangely the error seems intermittent so I have always been able to try again and get it to work, perhaps saving the section field by field.

Has anyone experienced this and/or can anyone suggest a fix? Thanks

CAn you list which fields are causing this error?

I suspect could be to do with SSM 3.0beta2 though I think it has happened with a simple text entry field which I have used to test the problem after getting the error within more complex sections.

I thought it might be server-specific, but today it happened on a completely different server.

Do you have any uninitialised extensions? Or empty folders in extensions? I once run into the same problem on Symphony 2.2.5 and it was caused by empty extension folders.

I don't have any empty folders but I do have quite a few uninstalled extensions. I'll try cleaning them out and see if I get any errors. Thanks

I got the same error on another much simpler installation with fewer extensions. There was one disable extension which I have now deleted. I'll look out for further errors.

Symphony Fatal Error: Could not find Field at /field..php. If it was provided by an Extension, ensure that it is installed, and enabled.

An error occurred in /srv/www/gousto.co.uk/public_html/sym/symphony/lib/toolkit/class.fieldmanager.php around line 524

519             if(!isset(self::$_pool[$type])){
520                 $classname = self::__getClassName($type);
521                 $path = self::__getDriverPath($type);
522
523                 if(!file_exists($path)){
524                     throw new Exception(
525                         __('Could not find Field %1$s at %2$s.', array('<code>' . $type . '</code>', '<code>' . $path . '</code>'))
526                         . ' ' . __('If it was provided by an Extension, ensure that it is installed, and enabled.')
527                     );
528                 }
Backtrace
[/srv/www/gousto.co.uk/public_html/sym/symphony/content/content.blueprintssections.php:611]
    FieldManager::create();
[/srv/www/gousto.co.uk/public_html/sym/symphony/lib/toolkit/class.administrationpage.php:602]
    contentBlueprintsSections->__actionNew();
[/srv/www/gousto.co.uk/public_html/sym/symphony/lib/toolkit/class.administrationpage.php:571]
    AdministrationPage->__switchboard();
[/srv/www/gousto.co.uk/public_html/sym/symphony/lib/toolkit/class.administrationpage.php:398]
    AdministrationPage->action();
[/srv/www/gousto.co.uk/public_html/sym/symphony/lib/core/class.administration.php:228]
    AdministrationPage->build();
[/srv/www/gousto.co.uk/public_html/sym/symphony/lib/core/class.administration.php:381]
    Administration->__buildPage();
[/srv/www/gousto.co.uk/public_html/sym/index.php:25]
    Administration->display();
Database Query Log
[0.0003] SET character_set_connection = 'utf8', character_set_database = 'utf8', character_set_server = 'utf8';
[0.0001] SET CHARACTER SET 'utf8';
[0.0003] SELECT SQL_CACHE t1.name, t2.page, t2.delegate, t2.callback FROM `sym_extensions` as t1 INNER JOIN `sym_extensions_delegates` as t2 ON t1.id = t2.extension_id WHERE t1.status = 'enabled' ORDER BY t2.delegate, t1.name;
[0.0002] SELECT SQL_CACHE `session_data` FROM `sym_sessions` WHERE `session` = 'aacdaoqph8flah5jb766e11ou2' LIMIT 1;
[0.0001] SELECT SQL_CACHE `id` FROM `sym_authors` WHERE `username` = 'stuart' AND `password` = '0e55c549efd545a1ff9d093a4a49ce661a880c14' LIMIT 1;
[0.0003] UPDATE sym_authors SET `last_seen` = '2012-07-26 14:54:39' WHERE `id` = '1';
[0.0004] SELECT SQL_CACHE * FROM `sym_authors` WHERE `id` IN (1);
[0.0002] SELECT SQL_CACHE `name` FROM `sym_extensions` WHERE `status` = 'enabled';
[0.0002] SELECT SQL_CACHE * FROM `sym_extensions`;
[0.0002] SELECT SQL_CACHE `s`.* FROM `sym_sections` AS `s` ORDER BY `s`.`sortorder` asc;
[0.0003] SELECT SQL_CACHE `id` FROM `sym_sections` WHERE `handle` = 'week' LIMIT 1;

Symphony Fatal Error: Could not find Field at /field..php. If it was provided by an Extension, ensure that it is installed, and enabled.

That says a lot to me. There is something wrong with an extension here as it isn't passing the field name forward to create the filename to include (see the two dots).

Hmmm. Did a grep of the extensions folder and then the while Symphony folder, no field..php.

Any ideas how I could debug this?

No, that file reference won't exist.

Symphony will use the value of self::__getDriverPath($type); to build the $path variable. If there is a bug in an extension then this function will return incorrect data, and not create the name of the field's file properly, resulting in field..php.

Should've explained better.

If this is happening on multiple servers, then I'd try reproducing it with only core fields. If it happens then, then log it on Github as an issue.

If not, try one field extension at a time to see which one it is.

I actually ran into this last night. I wasn't able to pinpoint the exact issue, but it was happening with core fields. Text Input for sure. I was having to add one field, simply giving it a name and nothing more and saving it first. After that it would behave just fine. If I made it required or anything before saving, I'd get this error.

I didn't investigate it a lot as I found that work-around, but I do have a few extensions installed. The only one that adds anything to the core fields is custom field captions, but I can't verify that it was the cause.

That's two cases of the same bug. Can someone log this on the issue tracker please?

Please include your installed extensions and steps to reproduce in that bug report, otherwise it's like hunting down Nessie.

Brendan, Nessie doesn't actually exist. You're wasting your time there in Scotland!

This just happened again and I logged the issue:
https://github.com/symphonycms/symphony-2/issues/1401

We have narrowed this down to the Custom Field Captions extension.

Are you using the integration branch of Custom Field Captions?

Edit I've made a couple of changes on the integration branch that should protect against this sort of error again. I haven't been able to reproduce since adding these checks and following the steps you said above.

I was using the master branch. I tested the integration branch but still get the error. My GIT skills are pretty rubbish, so I might not have upgraded properly. This is how I upgraded:

rm -R customfieldcaptions/
git clone -b integration git://github.com/brendo/customfieldcaptions.git

Need any more info?

Nah, that that will update it to the integration branch. Can you try clearing your browser cache, perhaps the javascript file is the same as it was before.

What's the exact steps to get the error to reproduce? What browser is this on as well?

Basically I'm fairly certain the error originates from an input's name being mangled, or the caption being placed outside the usual naming convention, which causes Symphony to thinks it's a new field. I haven't been able to reproduce it to confirm though.

What's the exact steps to get the error to reproduce? What browser is this on as well?

For me, it seems to do it if I add a Text Input field and do anything more than give it a name. If I checked to make it required before saving the section, I would get the error.

This was in Google Chrome v21, I didn't check in other browsers.