Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibilty ContentBox3 layoutservice not found #8

Closed
danielosan opened this issue Jul 27, 2016 · 9 comments
Closed

Compatibilty ContentBox3 layoutservice not found #8

danielosan opened this issue Jul 27, 2016 · 9 comments

Comments

@danielosan
Copy link

the layoutservice seem to be depreciated in CB3. Activation of the module fails with error
var layoutService = wirebox.getInstance('layoutService@cb');
line 36 in moduleconfig.cfc

@danielosan
Copy link
Author

LayoutService was replaced by ThemeService

lmajano added a commit that referenced this issue Jul 27, 2016
@lmajano
Copy link
Contributor

lmajano commented Jul 27, 2016

Thanks, fixed

@lmajano lmajano closed this as completed Jul 27, 2016
@danielosan
Copy link
Author

another...

moduleConfig.cfc Line 40 from
var layout = ThemeService.getActiveLayout();
to
var layout = ThemeService.getActiveTheme();

@danielosan
Copy link
Author

SlatwallSetup.cfc needs a increase of the requesttime <cfsetting requesttimeout=300/>

lmajano added a commit that referenced this issue Jul 28, 2016
@lmajano
Copy link
Contributor

lmajano commented Jul 28, 2016

done

@danielosan
Copy link
Author

Right know activation hangs on /org/hibatchi/HibachiSmartList.cfc with a null pointer at Line 790 orm query. Thus far I could not figure out why. Standalone installs fine.

@danielosan
Copy link
Author

because /slatwall/config/configApplication.cfm did not update with application-name, database and additional mappings. Did it manually, but more issues now regarding the binder slatwallSyncService not found in interceptor-slatwall

@lmajano
Copy link
Contributor

lmajano commented Jul 28, 2016

Hmm, I think now you might need to contact @gregmoser on this.

@gregmoser
Copy link
Contributor

@danielosan can you post the entire stack trace error on the Slatwall google group. It may be a bug in Slatwall in which case we can open an issue over there. Our google group can be found at: http://www.slatwallcommerce.com/community

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants