Richard Shackleton

My feedback

  1. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Kentico Product Ideas » Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton supported this idea  · 
    Richard Shackleton commented  · 

    All 3 would be valuable although I'd rather #2 use CKEditor so it is consistent with the admin site rather than expect content editors to be comfortable with two different WYSIWYG editors.

    This also means any custom extensions to the WYSIWYG only need to be built once.

  2. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Kentico Product Ideas » Content Management  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton shared this idea  · 
  3. 119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Kentico Product Ideas » Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton commented  · 

    +1 on Gabor's comments.

    Richard Shackleton commented  · 

    Has there been any movement on this since originally posted?

    Richard Shackleton supported this idea  · 
    Richard Shackleton commented  · 

    Agree with Sean on this one. The use of static Context classes causes a lot of tight code-coupling which causes issues with unit tests. Ideally the Contexts would be injected using interfaces which we could then mock in our tests.

    On the point of testing, there is still no ability to call a "SetInfo" method on an InfoProvider when writing a unit test. This also causes issues and requires a layer of abstraction on our side to avoid.

  4. 28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Kentico Product Ideas » Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton commented  · 

    Hi Martin,

    In terms of OWIN:

    We have needed to hook into the request pipeline in the past to make checks to redirect/rewrite requests based on business logic. Having the ability to do this as early as possible will remove some overhead on the initial request.

    Using the OWIN pipeline also allows us to separate the webforms environment and multiple WebAPI environments with their own specific configurations. We have had scenarios before where changes to the WebAPI configuration have impacted the Kentico dashboard as this also uses WebAPI.

    In terms of Identity:

    The main scenario we have encountered is using WebAPI in conjunction with Forms Authentication.

    There is a disconnect when doing this. However, if we could use the Identity framework then we could share the same authentication token between the two systems whilst maintaining a stateless API.

    The Identity framework also supports using OAuth with only simple configuration which will make the authentication more extensible with 3rd party services or SSO.

    Richard Shackleton commented  · 

    Hi Martin,

    Would Kentico be looking to implement this in the WebForms version also?

  5. 38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Kentico Product Ideas » Content Management  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton shared this idea  · 
  6. 96 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Kentico Product Ideas » Content Management  ·  Flag idea as inappropriate…  ·  Admin →
    Richard Shackleton shared this idea  · 

Feedback and Knowledge Base