Sellerdeck just keeps breaking and breaking and breaking

[Goz]

I've just placed an order on what I think is your main site and took it through to SagePay without issue (I realise it's an intermittent fault).

A couple of things I noticed.

Your Cart and Checkout pages are behind SSL but are displaying insecure content - the Secure Payments Using SagePage graphic and the Payments Method Accepted graphic are both delivered using http://

The Quick Search box in the header is too big and is pushing the social media icons down. If you change the CSS for .quick-search so that width is 60em rather than 70em then it will tighten the header up.


I'll keep looking around - do you want to PM the URLs for the other sites?

[Mike Hughes]

Hi Vicky,

What you're going through sounds like a nightmare but it's very unusual and unfortunately you now appear to be in a very bad place.

My thoughts on all this are:

1. Don't edit the sellerdeck .NET code (if that's really what's been happening)

- It can have unintended consequences
- You can't reinstall Sellerdeck without having to reapply any changes.
- You can'd update Sellerdeck without having to check and reapply any changes.
- Your software becomes unsupportable as no-one knows where any problems lie.

2. Not handing over correctly over to the psp is usually down to one of two issues. Either a problem with the smtp server which can cause a timeout in the sellerdeck perl scripts, or an HTML problem on the page that causes an issue with the DOM and the page to freeze. You mention someone saying it's a problem with the .net coding which worries me as that's only used in the desktop environment.

3. Two sites not sending any emails are a worry, there should be relevant errors in the error log and the network test should also highlight what the problem is. It's important to get this fixed for both the sake of emails and for the related problem with psp transfers.

4. If there's ever any odd behaviour in the database then the first step should be to compact and repair the database. This usually catches most problems and if any remain sellerdeck support can usually take a look if you send them a copy and find any outstanding issues.

5. Which version of the database do you have? is it the normal .mdb or the enterprise SQL? Not that I'm sure it makes much difference.

6. I've never come cross any cases where Sellerdeck is using two copies of the database. There could be many ways of fixing this by trial and error but I can't see how it could happen as the database always has a fixed name and location. I suppose it could be a corruption in the setup somewhere in which case a reinstall should fix it. Just be sure to keep an up to date snapshot somewhere safe.

7. I do find the 'Invoice on Account' payment method an odd one but I'd surprised if the mapping to sagepay couldn't be made to work properly. I don't use sagepay so can't help here. If the customer requests an invoice for payment rather than on account then I'm sure one of the other methods could be made to work.

8. Having payment types on orders that don't exist in sellerdeck will cause the order to crash on opening. This could happen if there's a mismatch between the 'creation' and 'order management' versions of the site or they ever become out of sync.

To me it sounds as if your Sellerdeck software needs a little care and attention. In your case I'd be looking to implement a rolling program across your sites to:

1. Reinstall the standard version of Sellerdeck with no changes to the underlying program.

2. Make sure all the network setup, email settings, payment types, shipping methods, etc are all setup correctly and map over to sagepay as desired. Test to ensure there are no error messages and everything works correctly. There is no reason why this shouldn't be possible.

3. In the event that there are still problems then come to the forum and see if we can help fix them. Most of the issues that people come across have been seen before and there's a huge base of experience here in setting up, using and identifying issues with Sellerdeck. This needs to be done from a stable base though which is why I'm suggesting steps 1 and 2 first.

[Vicky.Pearson]

Thank you both.

No .net programming has been done, it was just what Sagepay recommended. I am not a .net programmer and we do not have one on staff, but we have hired one to come in and have a look. He found the intermittent double databases but did not tinker with it to fix it, as we only paid him for so much time.

I have had Sellerdeck look over my databases at various points and the errors were never fixed, but I am trying to speak to someone today.

Will look into the other points and post back.

Thank you very much

[Vicky.Pearson]

I would also add, I am a html / css code specialist but mostly lean towards the graphic and appearance side of digital marketing and design. So trying my best with limited hard programming skills.

We have re-installed the software and updated to the latest version.

We have also moved internet servers to the SSL server, with problems continuing over these changes.

On the issue of the images being insecure, why would it do that if its all supposed to be set up for SSL?

[Mike Hughes]

On the issue of the images being insecure, why would it do that if its all supposed to be set up for SSL?

Typically, these are images where the reference has been manually entered as http:// rather than https://

Images maintained by sellerdeck are usually entered with just their local reference. i.e typically something like /images/myimage.jpg if you store images in an 'images' folder on the PC. These ones will automatically use https:// on upload when SSL has been set up.

Mike

[chris ashdown]

Is she using external links Mike where they are using data from outside selledeck?

[Mike Hughes]

I don't think so Chris. The sagepay and payments accepted graphics are both being served from their own web server.

[Vicky.Pearson]

Thank you, no idea why its not working properly then, as all our images are served using the root folder for Sellerdeck?

I will have another look into this and double check everything.
This is one of our frustrations, as there is no logical reason why it's not showing as secure.

[zgap111]

Using Firefox : click on padlock > more information > media tab

This will show up all the images etc and their links.

I can't seem to find the same info on Chrome or IE