Not sure if this is a Ctools issue, or a Core issue, so posting here first.

I just finished building a site in D8 and everything is running fine in my local dev.

I committed to git, and pushed everything to my remote shared repo, and then pulled it down to my staging, and attempted to set everything up as I usually do. I now get an error to the screen

Fatal error: Class 'Drupal\ctools\EventSubscriber\WizardControllerSubscriber' not found in /home/xxx/public_html/wp/core/lib/Drupal/Component/DependencyInjection/Container.php on line 264

I don't see that git missed anything important on the commit. My remote staging is not yet set up for working remotely with Drush for a D8 site, so I am committing the vendor/ directory to git as well, but I have done that before with good results. I ran all updates with composer before I committed and pushed, and but I can't see why it would not be working on my remote but working just fine on my dev. Why would the class not be found?

I also see an error in my error log on remote as follows

PHP Fatal error: Class 'Drupal\Core\StringTranslation\PluralTranslatableMarkup' not found in /home/xxx/public_html/wp/core/includes/common.inc on line 133

My local dev is in php 5.5.9, my remote staging is php 5.5.31

Does anyone have any sense of what is going on? I searched and did not find anything in the issue queue.

Comments

RKopacz created an issue. See original summary.

RKopacz’s picture

RKopacz commented
Issue summary: View changes
hkirsman’s picture

hkirsman commented

Same here. Worked locallay.

hkirsman’s picture

hkirsman commented

For now I did

git revert COMMIT-ID
composer install

and it's working again so must be something in 8.3.0-alpha27

RKopacz’s picture

RKopacz commented

Thanks @hkirsman, I'll try that. But I still don't understand why it works locally but not on the remote staging.

andrej galuf’s picture

andrej galuf commented

The Container is looking for the old EventSubscriber class, but it was converted to a newer version (RouteEnhancer), which causes an error. Rebuilding the cache should solve this problem.

RKopacz’s picture

RKopacz commented

@Andrej Galuf Thank you, that did the trick! Since I do not have a D8 compatible drush properly working yet on my remote, I cleared the cache on my local, then updated the remote database with the new dump, and it worked. Kind thanks!

fomenkoandrey’s picture

fomenkoandrey commented

Error: Class 'Drupal\ctools\EventSubscriber\WizardControllerSubscriber' not found in Drupal\Component\DependencyInjection\Container->createService() (line 264 of core/lib/Drupal/Component/DependencyInjection/Container.php).

have the same error, when updating the module.
now site doesnt work at all.

RKopacz’s picture

RKopacz commented

@fomenkoandrey try clearing the cache, it worked for me.

fomenkoandrey’s picture

fomenkoandrey commented

I replaced the extension files alpha27 from the archive with alpha26 files.
now site works, but update or clearing the cache - does not work, only white screen.

/admin/config/development/performance - clear cache - white screen.
/update.php - white screeen

UPD:
after attempting to clear the cache - site stopped working, all the pages - white screen (((
what to do?

UPD2: i try clear tables cache_dynamic_page_cache, cache_data, cache_render through PHPmyadmin - the same, all - white screen.

fomenkoandrey’s picture

fomenkoandrey commented

look like the problem with metatag beta10
with metatag beta9 - no errors.

hkirsman’s picture

hkirsman commented

I guess we need update function witch clear cache? In d7 I found clear cache functionality from module enable/disable function.

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

I got bite twice! On local update and on production.

The fix was to issue a drush cache-rebuild command.

Usually drush already does that when doing a drush up module-name. So I do not know why we need to fire up again cache-rebuild.

stewest’s picture

stewest
Location Wellington
commented

I'm also drush cr'd and still get the White screen with the error.

I rolled back to 8.x-3.0-alpha26 and still get the error. My site is down.

I then rolled back Meta tag as well to with metatag beta9 - and site still down.

danny englander’s picture

danny englander
(he/him)
commented

I just ran into the same error, entire site WSOD. Reverting back to the previous version with Git "fixed" it for me.

stewest’s picture

stewest
Location Wellington
commented

I had to go to CTools Dev, and remove Metatag totally.

tobias.streefkerk’s picture

tobias.streefkerk commented

Same here, got the problem after updating tot beta27. Reverting and checking out beta26 fixed the problem for me, for now.

dadangnh’s picture

dadangnh commented

Mine got this problem fixed after I use drush cache-rebuild command.

DeluxeSeika’s picture

DeluxeSeika commented

Same as #18, a drush cr all fixed this for me

TolliSysDev’s picture

TolliSysDev commented

#13 & #18 (drush cache-rebuild) did the trick for me as well.

chegor’s picture

chegor commented

I got this error and WSOD after update to 8.x-3.0-alpha27 from previous alpha. I cleared cache and all is ok now.

japerry’s picture

japerry
Location KOMK
commented
Category: Bug report » Support request
Priority: Major » Normal
Status: Active » Reviewed & tested by the community

I didn't mark it fixed yet, just in case others ran into this issue, but it seems like clearing the cache is good enough.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: » #2833310: Plan for CTools 8.x-3.0-beta1
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Component: Code » Documentation
Status: Reviewed & tested by the community » Active
Parent issue: #2833310: Plan for CTools 8.x-3.0-beta1 »

Seems like this is a documentation thing?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Closed (works as designed)

Actually going to mark this a "works as designed" thing, config and code deployments should always be accompanied by a cache clear.