• About Us
  • Blog
  • Basket
  • Account
  • Sign In
  •  

Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 23 Feb 2015 03:28 PM by  Kamila
(SOLVED) Issues after upgrading to Premium Data
 7 Replies
Sort:
Topic is locked
Author Messages

David Lievense



New Member


Posts:
New Member


--
15 Mar 2012 03:52 AM
    So here's our configuration on our test site (http://new.organicbouquet.com) which is not working: I've created a file called FiftyOne.lic in the /bin/ directory with the license sent to me in the Invoice email. <fiftyOne> <redirect firstRequestOnly="false" timeout="20"> <locations> <location name="mobile" url="http://m.organicbouquet.com{0}" matchExpression="(?&lt;=^\w+://.+/).+"> <add property="isTablet" matchExpression="false" /> <add property="isMobile" matchExpression="true" /> </location> </locations> </redirect> <log logFile="~/App_Data/Log.txt" logLevel="Debug" /> <detection binaryFilePath="~/App_Data/51Degrees.mobi-Premium.dat" /> </fiftyOne> However we're having two problems: 1.) Tablets (specifically iPad) are still redirecting to m.organicbouquet.com when they should stay on the site 2.) For some reason logging is not working now (although it was working before switching to Premium Data). The Network Service account does have read/write access to the App_Data folder. Thanks for whatever guidance you can provide.
    0

    Tom Holmes



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 10:46 AM
    It's puzzling that the log file is not being created when it had been before. Can you try restarting your sites app pool and see if it starts then? I've also just tried the site you gave with an iPad useragent and it redirected me to the mobile page. Are you still seeing the problem in your tests?

    Thanks,
    Tom
    0

    David Lievense



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 02:58 PM
    So I realized part of the problem was apparently due to sleep deprivation and I still had http://new.organicbouquet.com" target="_blank" rel="nofollow">http://new.organicbouquet.com pointing to our production site so all of the testing I was doing wasn't having any effect.  I've fixed that now and the Log file is properly generating.  Ultimate here's the behavior we need:

    1.) Any visit from a tablet (iPad, Xoom, Galaxy Tab, Nook Tablet, etc) should stay on http://new.organicbouquet.com" target="_blank" rel="nofollow">http://new.organicbouquet.com

    2.) Any visit form a mobile device should redirect to http://m.organicbouquet.com

    3.) If they visit a specific page (say from clicking through an email or a search result) on their mobile they should be redirected to that exact same page.  I.E. visiting http://test.organicbouquet.com/p_30...ilies.html becomes http://m.organicbouquet.com/p_3025/EcoBlooms/Flowers/Mixed-Flowers/peruvian-lilies.html

    When we were using the Lite version everything was working great (as you can see by visiting http://www.organicbouquet.com) EXCEPT that Tablets were being redirected as well.  And that's because we had this setup:

    <fiftyOne>
                <redirect firstRequestOnly="false" mobileHomePageUrl="http://m.organicbouquet.com" originalUrlAsQueryString="true" timeout="20">
                </redirect>

                <log logFile="~/App_Data/Log.txt" logLevel="Fatal" />
            <detection binaryFilePath="~/App_Data/mobidata.bin" />
    </fiftyOne>

    In order to solve #3 above I had to write some hacky parsing code in our mobile default page because the origURL parameter includes the full url instead of just the path & query, but as I was reading more it seems that you guys do support an automatic redirect that should alleviate the need for that code.

    So now the problem is that NOTHING is redirecting (based on the web.config from the first post).  I have the log level set to Debug and everything seems to be working correctly and the log (unfortunately) doesn't include any actual information on why it's forwarding or not forwarding a url (might be nice to fix that in future releases for troubleshooting purposes).

    Any guidance to why nothing would redirect any longer?
    0

    David Lievense



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 03:03 PM
    Oh and in case you need it here is the entries from the log file:

    2012-03-15T15:01:24.4114000Z - 2184 - Debug - Getting 'fiftyOne/redirect' configuration from the web.config file.
    2012-03-15T15:01:24.4270000Z - 2184 - Debug - Initialising Detector Module
    2012-03-15T15:01:24.4270000Z - 2184 - Debug - Initialising redirection module
    2012-03-15T15:01:24.4270000Z - 2184 - Debug - Initialising redirection module static fields.
    2012-03-15T15:01:24.4426000Z - 2184 - Debug - Initialising redirection module event handlers
    2012-03-15T15:01:24.4426000Z - 2184 - Debug - Initialising Detector Module
    2012-03-15T15:01:24.4426000Z - 2184 - Debug - Initialising redirection module
    2012-03-15T15:01:24.4426000Z - 2184 - Debug - Initialising redirection module event handlers
    2012-03-15T15:01:24.4582000Z - 2184 - Debug - Getting 'fiftyOne/detection' configuration from the web.config file.
    2012-03-15T15:01:24.4738000Z - 2184 - Info - Creating provider from binary data file '....\App_Data\51Degrees.mobi-Premium.dat'.
    2012-03-15T15:01:25.0354000Z - 2184 - Info - Created provider from binary data file '.....\App_Data\51Degrees.mobi-Premium.dat'.
    2012-03-15T15:01:37.9366000Z - 2184 - Debug - Initialising Detector Module
    2012-03-15T15:01:37.9366000Z - 2184 - Debug - Initialising redirection module
    2012-03-15T15:01:37.9366000Z - 2184 - Debug - Initialising redirection module event handlers
    2012-03-15T15:01:40.5730000Z - 2184 - Debug - Initialising Detector Module
    2012-03-15T15:01:40.5730000Z - 2184 - Debug - Initialising redirection module
    2012-03-15T15:01:40.5730000Z - 2184 - Debug - Initialising redirection module event handlers
    0

    Tom Holmes



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 03:33 PM
    Hi,

    I've tested your segment of web.config, I believe the problem is that you're using 'isMobile' and 'isTablet' instead of 'IsMobile' and 'IsTablet'. The capital I's should allow redirection. You should then find that redirects are logged, stating the redirected useragents and the location that caused it.

    I hope this helps. Thanks,
    Tom
    0

    David Lievense



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 04:12 PM
    Tom,

    That was it!  I knew it had to be something I was overlooking.  I do see the correct entries in the log file now.  Not sure if it's possible, but it might be nice if there was error checking for a situation like this in the future.  Or if it was made clear in the documentation that all attribute values are case sensitive.

    Thanks for your help!
    0

    Tom Holmes



    New Member


    Posts:
    New Member


    --
    15 Mar 2012 04:14 PM
    Glad to be of help. Thanks for the question, we'll consider how to best handle this kind of situation for the next release.

    Thanks,
    Tom
    0

    Kamila



    New Member


    Posts:
    New Member


    --
    23 Feb 2015 03:28 PM
    You can also check the correct name of the property on our Property Dictionary page.
    0
    Topic is locked