Announcement

Collapse
No announcement yet.

Beta Test

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Beta Test

    Bug List
    1. In the Admin, I click add product under a category, the correct category is not always entered into the Category code fields for the product.

    2. In Category Product List Layout the next previous buttons don't work. Both conditions EQ should be GT
    <mvt:if expr="g.Offset OR g.NextOffset">
    <mvt:if expr="g.Offset EQ 0">
    previous button
    </mvt:if>
    <mvt:if expr="g.NextOffset EQ 0">
    next button
    </mvt:if>
    </mvt:if>

    3. Product display template <title>&mvt:store:name;: &mvt:category:name;</title> this should be &mvt:product:name;

    4. There is no logout link on the ACNT page

    Recommendations:
    1. Provide more screen real-estate for the "content".
    I'm running 1280 x 1024
    There is a lot Blue space on the left making the left nav wider than it has to be.
    There is a lot of white space around the content making me scroll left/right on some screens and scrolling up/down more than I would like.
    The layout should be designed for 1024 x 768

    2. On the Buttons screen, below each heading, display the SMT item/token needed to display this button.
    i.e. Save:
    Text item: <mvt:item name="buttons" param="Save" />
    Image item: <mvt:item name="buttons" param="SaveL" />
    Ray Yates
    "If I have seen further, it is by standing on the shoulders of giants."
    --- Sir Isaac Newton

    #2
    Re: Beta Test

    5. In previous versions of Merchant I could count on the contents of g.screen always being upper case. This is no longer true in 5.5.

    Is this a bug or by design?
    Ray Yates
    "If I have seen further, it is by standing on the shoulders of giants."
    --- Sir Isaac Newton

    Comment


      #3
      Re: Beta Test

      Hi Ray,

      Originally posted by RayYates
      Bug List
      1. In the Admin, I click add product under a category, the correct category is not always entered into the Category code fields for the product.
      I can't reproduce this error. Any special circumstances you used to reproduce it consistently?

      Originally posted by RayYates
      2. In Category Product List Layout the next previous buttons don't work. Both conditions EQ should be GT
      <mvt:if expr="g.Offset OR g.NextOffset">
      <mvt:if expr="g.Offset EQ 0">
      previous button
      </mvt:if>
      <mvt:if expr="g.NextOffset EQ 0">
      next button
      </mvt:if>
      </mvt:if>
      I believe Dave already fixed this for Beta3. The correct code is
      if Offset/NextOffset NE 0.

      Originally posted by RayYates
      3. Product display template <title>&mvt:store:name;: &mvt:category:name;</title> this should be &mvt:product:name;

      4. There is no logout link on the ACNT page
      Dave is still working on cleaning up the design so I'll make sure he's aware of this.

      Thanks,

      Alex
      Alex Kruglyak
      Software Engineer
      Miva Small Business Solutions
      http://www.mivamerchant.com

      Comment


        #4
        Re: Beta Test

        Originally posted by RayYates
        5. In previous versions of Merchant I could count on the contents of g.screen always being upper case. This is no longer true in 5.5.

        Is this a bug or by design?

        This isn't something we've changed in 5.5. Can you be more specific where you're seeing this error and how you're using the variable?

        Thanks,

        Alex
        Alex Kruglyak
        Software Engineer
        Miva Small Business Solutions
        http://www.mivamerchant.com

        Comment


          #5
          Re: Beta Test

          If you enter a url with Screen=ACNT it works.

          If you enter a url with SCREEN=acnt if fails (i.e. grey merchant error screen of death)

          Using Screen=CTGY and Screen=ctgy does display the correct screen but if I test for the value of g.Screen it should always be uppercase.

          <mvt:if expr="(g.Screen EQ 'CTGY') AND (g.Category_code EQ 'new_products')">

          do something...

          </mvt:if>
          It is often necessary to test for the screen value and it has always been stored internally as uppercase.
          Ray Yates
          "If I have seen further, it is by standing on the shoulders of giants."
          --- Sir Isaac Newton

          Comment


            #6
            Re: Beta Test

            I believe this was the case for MM4 and older.

            If you enter the URL with screen=plst, it should always fail in MM5.
            The variable "screen" is not case sensitive; however, the value must always be upper case.

            Pre-MM5 we did not have this restriction, but when the product was re-written this was changed.


            Thanks,

            Alex
            Alex Kruglyak
            Software Engineer
            Miva Small Business Solutions
            http://www.mivamerchant.com

            Comment


              #7
              Re: Beta Test

              I'm not sure I agree. Lowercase "plst" works. See these examples.

              This Works http://mm55.hostasaurus.com/mm5/merc...st&Screen=plst

              View source and you will see <body id="plst">
              where <body id="&mvt:global:screen;">

              This fails http://mm55.hostasaurus.com/mm5/merc...st&Screen=acnt

              However this works http://mm55.hostasaurus.com/mm5/merc...st&Screen=ACNT

              In my example above this conditional would fail <mvt:if expr="(g.Screen EQ 'CTGY')"> would fail if the link was ctgy.

              I think many sites test the g.Screen variable assuming it will always be uppercase.
              Ray Yates
              "If I have seen further, it is by standing on the shoulders of giants."
              --- Sir Isaac Newton

              Comment


                #8
                Re: Beta Test

                That's interesting.
                I just ran some tests on both mm5 and 5.5 and none of the pages seem to load when the value of g.Screen is lowercase.

                The case-sensitivity is probably server specific and from the brief test I ran on your site, I noticed that the only failed-to-load-pages are virtual pages (ACNT, AFAE, OUSL, OINF).

                I'd have to research further but if I was to guess...I'd say since these page codes should be re-written based on some criteria, they are not being matched properly because of their case.
                If the virtual page check fails, Miva Merchant assumes it's an actual page and tries to render it. The page load fails and the error is displayed.

                Thanks,

                Alex
                Alex Kruglyak
                Software Engineer
                Miva Small Business Solutions
                http://www.mivamerchant.com

                Comment

                Working...
                X