Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • AbsolutelyN 18 posts 173 karma points
    Mar 20, 2018 @ 11:10
    AbsolutelyN
    0

    Error: /umbraco/backoffice/InnerContent/InnerContentApi/GetContentTypeInfos

    Hi

    I've been struggling to get Stacked content to work ever since the problem of the blank pane on the right when you click to create a stacked content element as mentioned previously.

    I tried installing the alpha as suggested in another thread but not being familiar with how exactly to do this failed to understand exactly how to do this and it just got my project in a dll hell knot.

    I'm trying to get stacked content to work on Umbraco version 7.9.2 assembly: 1.0.6634.25789. .Net framework of project is 4.6.2. I've installed Stacked content 1.1.0 via NuGet in visual studio. This installed Inner content and Inner content core all version 1.1.0.

    When I click to add a stacked content element I now get this error:

    Request error: The URL returned a 404 (not found): /umbraco/backoffice/InnerContent/InnerContentApi/GetContentTypeInfos

    "MessageDetail":"No action was found on the controller 'InnerContentApi' that matches the name 'GetContentTypeInfos'."

    If anyone could point me in the right direction it would be much appreciated.

    Many thanks!

  • Lee Kelleher 3878 posts 14604 karma points MVP 9x admin c-trib
    Mar 20, 2018 @ 12:39
    Lee Kelleher
    0

    Hi AbsolutelyN,

    A month?! Yikes! Was this issue raised elsewhere? As I didn't see it.

    From looking at the error you mention, the GetContentTypeInfos call was renamed, (in v1.1.0, to GetContentTypesByGuid but that doesn't really matter) ... what does matter is that whatever is making the call to the old method name hasn't been upgraded.

    I'd say double-check that the "/AppPlugins/InnerContent" and "/AppPlugins/StackedContent" folders have the latest version in them. If they do, then I suspect that the old JS is cached somewhere - either in your browser itself or with ClientDependency.

    Try bumping the version number in the "/config/ClientDependency.config" file.

    Hope all this helps?

    Cheers,
    - Lee

  • AbsolutelyN 18 posts 173 karma points
    Mar 20, 2018 @ 13:52
    AbsolutelyN
    0

    Brilliant, thanks Lee. A force refresh of the browser cache completely solved it, should have thought of that earlier! Much appreciated.

Please Sign in or register to post replies

Write your reply to:

Draft