Code Monkey home page Code Monkey logo

epicweb.optimizely.redirectmanager's People

Contributors

lucgosso avatar

Watchers

 avatar

epicweb.optimizely.redirectmanager's Issues

Invalid column name after update

Hi, I've followed the instructions in the README in order to upgrade from an old version to this new one. It says to rename "the table" to 'SEO_redirect', so I've renamed a table named 'SOLITA_Redirect' as instructed.
I think this instruction could be clearer, as it was not clear to me which table should be renamed. The README also says "the schema" should be the same. I think this could be clearer as well, perhaps specifying the expected schema would avoid some confusion.

My end result is the following:
SqlException: Invalid column name 'Host'. Invalid column name 'Host'.
and
InvalidOperationException: The exception handler configured on ExceptionHandlerOptions produced a 404 status response. This InvalidOperationException containing the original exception was thrown since this is often due to a misconfigured ExceptionHandlingPath. If the exception handler is expected to return 404 status responses then set AllowStatusCode404Response to true.

So based on the first message I'm assuming the schema is not the same? Not sure what the second one is about.

I would appreciate some help with this, in the mean time I suppose I'll start perusing the source code of this repository. Thanks in advance.

Automatic Creation of Redirection Rules when Editing Content

Hi,

I've been using RedirectManager 6.0.0 along with EPiServer.CMS 12.22.5, and I've come across an issue that I'd like some guidance on.

Every time one of our editors saves a page, it seems to create a new redirection rule with the wildcard selected. While this might not be problematic in most cases, it's causing the redirection to the same page with the wildcard when attempting to access a non-existent page. This becomes particularly troublesome when editing the FrontPage. Essentially, it generates redirections with wildcards to the FrontPage, resulting in all non-existent pages being redirected to the FrontPage.

This behavior prevents us from displaying the 404 page for non-existent links. Moreover, it's generating multiple duplicate rules, cluttering the setup unnecessarily.

image

I'm reaching out to see if there's a specific configuration setting that I might be overlooking or using incorrectly. Alternatively, I'd appreciate any guidance on the best approach to resolve this issue.

Thank you in advance for your assistance.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.