Announcement

Collapse
No announcement yet.

Warning Message on Site Update

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

    Warning Message on Site Update

    Recently, when I update the site with minor changes I get the following message just before the upload begins:-

    "Warning: Some files on the website appear to have changed since Actinic Ecommerce last uploaded them. These files will be completely refreshed. The changed files are: oldtext.fil, oldprice.fil, oldprod.fil."

    They are always the same file type and always "old...", the site then proceeds to completely refresh. Although this doesn't pose a big problem, it is time consuming with rather a large site, and a little irritating.

    Can anyone shed some light on what might be happening?

    Mark

    #2
    Hi there

    Might be an idea to ftp to your site and check if the .fil have a permission of 777. If they don't, then please set their permission to 777. This should get rid of your warning message

    Kind Regards
    Nadeem Rasool
    SellerDeck Development

    Comment


      #3
      Warning messages

      Hi Nadeem,
      Thanks, I'll give it a try.
      Mark

      Comment


        #4
        Site Updates

        I have FTP'd to my site and attempted to change the permissions for the .fil files but I get "operation not permitted". I'm not sure why as I can change permissions on everything else. I also don't understand why these files are being changes outside of Actinic. I'm mystified??? Don't know what to do!
        Mark

        Comment


          #5
          Are the files owned by your username can you see when you login via FTP, i.e. if your username for ftp access was jobbloggs, is that what is shown next to them, or is it something else like apache or something like that maybe?

          Comment


            #6
            Using LeapFTP I cannot see any username next to the files. The file properties show Owner: 99 Group: 99 with a permission setting of 600 next to the offending .fil files. Most of the other files have a permission setting 644 and show Owner: 102 Group:30. In fact the acatalog directory shows Owner: 102. Could this be the problem and if so, how can I fix it?
            Mark

            Comment


              #7
              Get your host to chown the files to your username so that the UIDs all match up and also ensure that the chgrp is conducted so that this matches up with your files... This is assuming ofcourse though that they are using some sort of susexec method on your filespace and files, but once that is done then you should be able to amend the file permissions all yourself.

              Comment


                #8
                I have managed to chown some of the offending .fil files and have changed the file permissions to 777. Is this setting not a security risk? Does it not enable these files to be changed by anyone who may access the server? Should I change all the .fil files to 777?
                Mark

                Comment


                  #9
                  Hi there

                  Is this setting not a security risk? Does it not enable these files to be changed by anyone who may access the server?
                  Do be honest, someone can have access to your server, if they have your ftp username and password. If they don't have this, then they cannot change the content of the .fil

                  Should I change all the .fil files to 777?
                  Yes

                  Kind Regards
                  Nadeem Rasool
                  SellerDeck Development

                  Comment


                    #10
                    Warning messages

                    Many thanks to you all for your help in this matter.
                    Mark

                    Comment


                      #11
                      Warning messages

                      Hi again guys,
                      Problem not quite solved I've discovered. I carried out an update, after which I FTP'd to the acatalog directory and checked the files I had changed. They had reverted not only to the original file permissions of 600 but had also reverted to the original ownership of 99? I attempted to change them again but got "Operation not permitted" again, which means going back to the server and chowning them again.
                      What's a guy to do? Any clues?
                      Mark

                      Comment


                        #12
                        When Perl carries out an operation (e.g. creating a file during a merge) it seems to change the ownership of that file, so that it cannot be done a second time.

                        Check the ownership of the actual *.pl and *.pm files in the 'cgi-bin'. If they are chowned to '99' try changing them to something else. That might stop them messing up the *.fil files.

                        Comment


                          #13
                          Warning messages

                          All the Perl files are the correct ownership. What I don't understand is why the ownership of the .fil files are different in the first place. On another small actinic site I created the .fil files have the same ownership as the rest of the catalogue. I'm a bit stumped with this one???
                          Mark

                          Comment


                            #14
                            Hi Mark

                            It could be possible that it similar to this kb article. Please click here to read it

                            Kind Regards
                            Nadeem Rasool
                            SellerDeck Development

                            Comment


                              #15
                              Warning messages

                              Thanks Nadeem, I'll look into it.
                              Mark

                              Comment

                              Working...
                              X