Announcement

Collapse
No announcement yet.

Perl file truncated

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

    Perl file truncated

    Hi there

    In brief - client was trying to publish changes to his site and got an error on the Merge stage saying it was either corrupt perl files and to try a purge and refresh, or a permissions issue. We checked the permissions, even though nothing had changed on the server in months but just in case. Nothing. Did a purge and refresh finally, after trying a few ftp settings changes etc but when all is said and done we're still getting the same error. However it does appear that some changes are being published as we can suspend orders and reenable the basket button and that works fine.

    The main thing is - sorry to be long-winded but just in case above error has anything to do with it - when you try to add to basket you get a 502 error and it gives details of perl errors. It seems to be in the al00000x.pm file - it is truncated at line 5268 - it just stops:

    Code:
    if ($nResult != $::SUCCESS)
    {
    $Self->{_CONNECT_STATUS} = $::FALSE;
    So nothing works. This error was there before the purge and refresh, and we have changed the Id in network set up so it has got new files from Originals folder. The previous id was 2 and al00002.pm is also truncated, about 200 lines previously. al00003,pm seems to have gotten further, but still not the full size.

    Looking in the Originals folder, there is no sign of the al00000x.pm etc type files that end up in the cgi-bin folder. Can someone explain how these files are constructed and/or how I would ensure the file is complete? Or any insights at all would be great, thanks!

    #2
    First check and see if your system is using Internet Explorer 11. This may have been automatically installed as a Windows update and it breaks SD11.0.4 and below. See http://community.sellerdeck.com/show...9UIKP5,74E7G,1 for info.
    Norman - www.drillpine.biz
    Edinburgh, U K / Bitez, Turkey

    Comment


      #3
      Thanks a million! That was it - did take a publish and a refresh but the merging worked and now there are no more errors, so sorted, thanks!

      Comment

      Working...
      X