1.8 Alpha3 - Layout Edit Fails to Save

When going to layouts and then trying to selected and edit a display, when clicking on save I get this message:

( ! ) Fatal error: Class 'Xibo\XMR\CollectNowAction' not found in C:\wamp\www\xibo18alpha\lib\Entity\Display.php on line 527
Call Stack
#	Time	Memory	Function	Location
1	0.0006	163048	{main}( )	..\index.php:0
2	0.1569	2308688	Slim\Slim->run( )	..\index.php:120
3	0.1570	2309136	Xibo\Middleware\Xmr->call( )	..\Slim.php:1302
4	0.1570	2309984	Xibo\Middleware\Storage->call( )	..\Xmr.php:38
5	0.1571	2311696	Xibo\Middleware\State->call( )	..\Storage.php:46
6	0.4881	3880672	Xibo\Middleware\CsrfGuard->call( )	..\State.php:103
7	0.4881	3881056	Xibo\Middleware\WebAuthentication->call( )	..\CsrfGuard.php:62
8	0.5056	4815672	Xibo\Middleware\Theme->call( )	..\WebAuthentication.php:130
9	0.5068	4817896	Xibo\Middleware\Actions->call( )	..\Theme.php:73
10	0.5068	4818416	Slim\Middleware\MethodOverride->call( )	..\Actions.php:96
11	0.5069	4818608	Slim\Middleware\Flash->call( )	..\MethodOverride.php:92
12	0.5070	4818880	Slim\Slim->call( )	..\Flash.php:85
13	0.6131	6265992	Slim\Route->dispatch( )	..\Slim.php:1357
14	0.6131	6266224	call_user_func_array:{C:\wamp\www\xibo18alpha\vendor\slim\slim\Slim\Route.php:468} ( )	..\Route.php:468
15	0.6131	6266352	RKA\Slim->RKA\{closure}( )	..\Route.php:468
16	0.6247	6836088	call_user_func_array:{C:\wamp\www\xibo18alpha\vendor\akrabat\rka-slim-controller\RKA\Slim.php:79} ( )	..\Slim.php:79
17	0.6248	6836496	Xibo\Controller\Layout->edit( )	..\Slim.php:79
18	0.6509	7020168	Xibo\Entity\Layout->save( )	..\Layout.php:398
19	0.6616	7021120	Xibo\Entity\Layout->update( )	..\Layout.php:474
20	0.6772	7082448	Xibo\Entity\Campaign->save( )	..\Layout.php:1073
21	0.6840	7082368	Xibo\Entity\Campaign->notify( )	..\Campaign.php:217
22	0.7307	7298048	Xibo\Entity\Display->save( )	..\Campaign.php:415

@dan, I reverted the vendors folder to before I ran composer and the error went away.

Xibo\XMR\CollectNowAction used to be in vendors, but we moved it into /lib/XMR because it made more sense to have it in the CMS repository and to keep XMR “dumb”.


The only way I can think you’d get this error is if your composer.lock file is out of date compared to your main code base.

The code in composer and the source code itself are paired so that each time you get a new commit you also get a new composer.lock file containing any library changes between the versions.

I believe you are still working with the code in the develop branch? If so your routine workflow should be:

  1. git pull
  2. composer install --no-dev
  3. Manually check the latest /install/steps/N.json file for DB changes that you need to run

The first of these statements pulls in the updated code, the second the updated dependencies.

Humm… Not sure how that could be, we last loaded the Alpha3 version, and not the latest dev version. Although we did have that other trouble. But we will soon reload again to make sure and see if these issues still persist. Thank you for the information and guidance.

That’s not as odd as you’d imagine.

If you are updating composer on the alpha3 released files, they will pull in the latest version of the xibosignage/xibo-xmr library, which has been changed to remove those extra files.

When we actually release, we’d fix the version numbers

Ok. Thank you for the info!

1 Like