4 replies to this topic

[Joshua Eichorn]

This has been a consistent problem for us at Pagely as we have been migrating blogs to a new setup.  Anytime I move a site, tubepress fatals trying to calling a method on a non object.

 

The issue seems to be that the finder can't find the storageManger

 

src/main/php/add-ons/core/classes/tubepress/addons/core/impl/listeners/boot/OptionsStorageInitListener.php

$storageManager = tubepress_impl_patterns_sl_ServiceLocator::getOptionStorageManager();

 

is returning null

 

The same thing happens in 

src/main/php/classes/tubepress/impl/context/MemoryExecutionContext.php

 

There seems to be some sort of cache for the finder, but I can't figure out where its storage to clear things out.  I've bypassed it in the pass by hacking up tubepress_impl_patterns_sl_ServiceLocator, but managed to lose my notes and I don't remember what I did.

 

 

Any feedback would be appreciated.

 

-josh 

[Joshua Eichorn]

Dug into the error a bit more, 

 

I've traced it to

src/main/php/classes/tubepress/impl/ioc/IconicContainer.php

get method

 

The delegate doesn't know about tubepress_spi_options_StorageManager

 

seems like it would be more reasonable to throw a runtime exception here instead of returning null. That things would at least blow up in a debuggable way, instead of down the chain at a caller who always excepts the service provider to return an instance.

[Joshua Eichorn]

So it seems it was a bad rule in the rsync that was keeping the wordpress plugin directory from being copied.  The storage manager is provided by the wordpress plugin.  In any case, my comment above about throwing the exception on trying to get the tubepress_spi_options_StorageManager service back still holds, would have made this much easier to debug.

[brandon]

Josh,

 

I have notified our Lead developer about this.

 

Thanks!

[eric]

Thanks for your feedback, and I apologize that we caused headaches for you. So that this doesn't slip through the cracks, I've filed an issue on GitHub. Looking forward to implementing the fix.

 

If you have any other questions or feedback, please send it our way. Thanks!