Close

Profile: Boyko

Avatar

User posts

jakubz wrote:
Hi! how can I do this in 3.60? 


Hi jakubz,

All you need to do is explained in this post.

9 years ago

Oakstone wrote:
Implementing Cloud Zoom 3.2 on the Lighthouse template, the share buttons and the SKU do not display now. Is this just due to CSS? If so, how can I enable it?

Thank.


Hi Oakstone,

The Cloud Zoom comes with the Lighthouse theme and should already be working fine.
Not sure how the Cloud Zoom relates to the SKU and share buttons but please provide a link to your store, so that we can take a look and advice.

mkzaman wrote:

I have fresh installed nopcommerce and I installed real one page checkout. Each time, I refresh the checkout page a new value inserted in nop Address table. What's the problem here ?


Hi mkzaman,

I would like to inform you that you can now download the latest version of the plugin.
The plugin does not create new addresses every time after each refresh anymore but it reuses the existing addresses.
As a matter of fact the plugin needs to create 2 temporary addresses used during the checkout.
One for the Billing Address and another one for the Shipping address.
These addresses are needed since they are used by the Shipping and Payment providers as well as the Tax providers in nopCommerce. This way the customers that checkout can have up to date information about their order total, available shipping and payment methods etc.,
while they make changes to the addresses i.e changing the country.
So it is inevitable to have these 2 checkout addresses. 
The actual problem was that we created 2 new addresses each time the customer does a checkout, which should't happen and we should reuse these addresses.
Now we reuse this addresses and we don't create new ones if they already exist.

Please note that these changes don't affect the functionality of the plugin. The plugin was working fine with or without the fix.

9 years ago

codicezerouno wrote:
Hi Stanev,
problem solved after updating with latest binaries.

This means that the version "3.6.426.16755" of "Core" plugin, I was using before, causes the error.

Thanks


Hi codicezerouno,

That is strange. Maybe you have had some version missmatch i.e some plugins are different version that the Core plugin or you have added a new plugin that requires a newer version of the Core plugin. Anyway just in case I need to remind you that you should always update the Core plugin when you add new plugins.

9 years ago

joster wrote:
Oh...OK. That is unfortunate.
Thanks for the explanation.


Yes, it is unfortunate.
I really wish things were simpler for us as plugin vendors and for you as customers using our products but this is how it is for now.

9 years ago

joster wrote:

Hello-

I understand what you are saying, however, is it possible for you to share which changesets in the nopcommerce core that were added for 3.60 which your plugin requires? I ask because I have version 3.40 and will not be upgrading, and would gladly(and possibly already have) add those changesets which make it possible to use the RichBlog plugin.

Thanks!


Hi joster,

Here is the changeset that we asked Andrei to do specifically for the RichBlog plugin and this is the reason why we didn't release the plugin for nopCommerce 3.5. We waited for this changeset in order to be able to release the plugin.
http://nopcommerce.codeplex.com/SourceControl/changeset/f240106ff019d347b7bc7ce5dc92f5274159ee33

I don't see how knowing which changeset is needed could help you run the plugin for nopCommerce 3.4. Please note that there might be other changes since nopCommerce 3.4 to nopCommerce 3.6 that could possibly cause problems. 
As you know nopCommerce is not backward compatible with previous versions there are a lot of breaking changes between the different releases. That is why you can't have a plugin (no matter which one) for one version to work for the previous or next version.

9 years ago

codicezerouno wrote:
I got the error in a clean nop installation without any other plugin except those provided with nop binaries.
So, I supposed that anyone changed the route you mentioned.

The strange thing is that the error is not thrown if the project runs in Visualstudio.


Hi codicezerouno,

I can confirm that the plugins work perfectly fine with the default nopCommerce installation.
The only reason I can think of is that something is missing on your server.
Could you please double check if all files are uploaded on your server?
For example you can compare that the local files in the SevenSpikes.Core plugin folder are present on your server as well.

9 years ago

jakubz wrote:
Maybe you can start talking about it with nopcommerce team? Version 3.70? I think this is one of the most important "change" to improvement nopcommerce solutions. I have lots product out of stock.

Do you thinking it is possible? Maybe you are talking with nopcommerce team and other companies about this improvement?


Hi Jakubz,

Can you explain how exactly you are using the stock quantity?
Do you use the stock quantity on the various product attribute combinations or you simply use the field on the product itself?

9 years ago

codicezerouno wrote:
Hello,
I would need to run a new color.

I can, in some way, add a new color from the administrative panel?
thanks


Hi codicezerouno,

You can't add new color presets from the administration.
But you can edit any of the existing ones and simply change the existing color to the one you want.

9 years ago

codicezerouno wrote:
I tried to install Sevenspikes.core plugin in a clean nop 3.60, but after that the site throws the error


Please double check that you have not changed this route "Admin_default".
This route needs to be present otherwise our plugins will throw this error.
Maybe you are no changing it directly but some other plugin you have removes this route, while it shouldn't.

Please let me know if this is the case!