I'm guessing that your script path is wrong, it can be a little bit tricky to figure out what the correct path is. Did you watch the installation tutorial video?

Just released BitShop v1.0.4. It includes improved email headers which will decrease the number of emails sent by BitShop being flagged as spam. It also includes a fix for a minor XSS vulnerability on the contact page and a fix for a session bug which can occur when using the coinbase API. Download new version from client file area.

We can't fix it until we discover what is causing it. The bugs only seem to affect a small percentage of Windows machines so it's hard to diagnose. Cryptonite-Qt works absolutely fine on all my Windows machines so I have no clue what the issue is. And our main developer doesn't even use Windows.

I don't really have a clue, you're the only person who seems to be having that issue. It seems like your database is behaving oddly. That error indicates that the transaction could not be located in your database, but in order to reach that point the transaction must have been inserted into the database. It's really an error which should never happen.

The first half of this video I made explains it fairly well: https://www.youtube.com/watch?v=Eb0sAmQD0Dk

My guess would be that you don't have curl installed.

The max block size is 2 times the average size of the last hundred blocks. So if the last 100 blocks had an average size of 5MB then the max block size for the next block would be 10MB. The lower limit is 2MB to ensure that tx's will always get into the block.

The problems seem isolated to only some Windows machines. I think the issue may have something to do with the Visual C++ Redistributable Package or some other package which is installing incompatible system dll's which Cryptonite is trying to use. Do any of you guys have Visual Studio installed?

Nothing is dead, I have started work on the client side encrypted web wallet but it's turning out to be much harder than expected. I took a look at the brain wallet javascript code and realized they are actually building the entire transactions in javascript, which isn't much help to me because Cryptonite tx's have a totally different structure. So my only option at this point seems to be to rewrite all that code. I should be able to figure it out but it's going to be a pain in the ass and I have other jobs I need to get done, so I'm willing to pay up to 0.5 BTC to anyone who can rewrite the code to correctly sign a raw Cryptonite transaction.

I'm not sure what the problem is so I can't tell you how to fix it. I would need admin access to your site in order to properly diagnose the issue. If you have any PHP knowledge you should be able to work it out yourself. Problem was incorrect coinbase settings.

I'm guessing that $use_coinbase is returning false in the sci/process-order.php file. Several people are using the coinbase API so I know it works. If you're testing it on a local server that's probably why it wont work. It will fall back to the default payment gateway if it can't reach the coinbase API.

It just uses the coinbase.com API to process your payments, meaning your wallet will be managed by coinbase instead of having to manage the keys yourself. Read the /install/coinbase.txt file for the setup instructions.

The headers have already been sent, but session_write_close() was called before session_start() was called for a second time. But apparently that doesn't work properly on all versions of PHP. I didn't write this part of this script so I don't know if it always had this issue. But the fix I described above should work according to this stackoverflow question.

Open the buy.inc.php file and add this code after line 20:

     ini_set('session.use_only_cookies', false);
     ini_set('session.use_cookies', false);
     ini_set('session.use_trans_sid', false);
     ini_set('session.cache_limiter', null);

A 500 error is what should happen when you test it in coinbase, because it's not providing any legit transaction data to the script.

That means your server is unable to make any remote connections, check that you have curl installed.

Sorry the contact form is currently not working due to a stupid filter put in place by my host.

You cannot export keys if you have no keys in your database (notice it says "there are no keys yet").

Yes that is a legitimate point, that's why we will implement account tree pruning at some point in the future. Lowering the level of decimal places is not a feasible solution. Low balance accounts need to be removed from the account tree after some period of time. The exact details of how it should work is still undecided because it's a very complicated subject.

Depends on how complicated the job is. Got a lot in the pipe right now.

Ok I think the best solution is the following.

Open /inc/themes/default/side.inc.php and replace this line:

          <ul class="nav nav-list" style="padding:8px 0;">

With this line:

          <ul class="nav nav-list">

In other words just remove that inline style, I shouldn't have done that.

Then open your /css/main.css file and replace this block of code:

#side_nav {
   padding:14px;
   padding-top:0px;
   padding-bottom:0px;
}

With this block of code:

#side_nav {
   padding:0px;
}

Also restore the original bootstrap.min.css file for the slate theme.

Yeah this fix wont be as simple as I thought it'd be. I'll probably need to edit the .less files and then generate a new .css file (now you know what the .less files are for). Although your fix seems to be a good enough solution for now.

Are you sure you uploaded the modified css file? I just checked and it seems to be exactly the same (http://spend-ur-bits.com/css/bootstrap.min.css).