Announcement

Collapse
No announcement yet.

A General Script Error Occurred

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

    A General Script Error Occurred

    I have two price schedules on my clients site.
    Customers that DO NOT log in GET a discount, and
    customers THAT DO log in, DON'T GET a discount.
    (I know, sounded backwards to me too, but that
    is the way my client wanted it).

    I have noticed that when ever customers
    just go shopping, without logging in, that
    the links from a site search results page
    produce an error message when clicked on.
    The error reads as follows:
    """A General Script Error Occurred
    ---------------------------------------
    Error:
    ---------------------------------------
    Press the Browser back button and try
    again or contact the site owner"""

    Any thoughts on this one?
    Best Regards,
    John King
    Web Master - BizPlus2000.com
    Web Hosting and Design for Today's Internet!
    Visit <a href="http://bizplus2000.com">BizPlus2000.com</a>

    #2
    Hi John

    There is a bug in 6.1.2 in ActinicPXML.pm that causes this error. There is however a fix.

    Edit Actinic.PXML in your site folder with notepad. (make a backup before you begin.

    Search for # Handling error


    Imediately above

    #
    # Handling error
    #


    insert

    else
    {
    $nScheduleID = $ActinicOrder::RETAILID;
    }



    The save ActinicPXML.pm and update the website.

    I hope this helps.
    Darren

    SellerDeck

    www.sellerdeck.co.uk

    Comment


      #3
      Thanks Darren

      Your fix worked out nicely. Is this going to be an issue
      when I run the site upgrader while upgrading to 6.1.3?
      Best Regards,
      John King
      Web Master - BizPlus2000.com
      Web Hosting and Design for Today's Internet!
      Visit <a href="http://bizplus2000.com">BizPlus2000.com</a>

      Comment


        #4
        when I run the site upgrader while upgrading to 6.1.3
        Yes and no, the perl scripts will be upgraded to the latest versions, but as the bug is fixed in 6.1.3 you will not have this problem again.
        Darren

        SellerDeck

        www.sellerdeck.co.uk

        Comment

        Working...
        X