Complete Order - Direct Link to new product review

Perhaps I can make the necessary changes to my 3.40 version to allow for the new token code to be utilized?? I mean, surely you are not just trying to force me into upgrading my theme and plugin licenses just to gain access to a message token...right?

I mean...if you are just looking for a way to get paid for adding the feature into an older version, I will pay for the renewal to the license...but I have no intention of upgrading my nopcommerce version number.

Hi Joster,

It is not a matter of paying for it. If we were able to do it we would but as I said it there is a technical problem in nop 3.4 that doesn't allow us to do it there. I don't want to go into technical details as I think you got the point here.

OK, so your company could not even be hired to make the customization because it is too difficult for you?

Hi Joster,

I don't think you got the point here.
The changes are not difficult they are just not possible to be done in 3.4.

I wish I could edit my replies.....

I don't mean to be obtuse, but my company needs this capability and I must endeavor to find a viable solution. Whatever the cost, and from whomever can provide it. If the version of the product I purchased from you (barely a year old) cannot be easily modified to include the same functionality as newer version, I understand...but it is almost impossible for me to believe that you guys are not capable of achieving it.

I'm fairly certain that your code is obfuscated, and therefore I wouldn't be able to provide another developer with the source code and hire them to make the modification. Right?
So, unless you guys can be contracted to make the modification for me, I must hire another developer to re-create the entire plugin for me....which I'll do if I have to.

You're right. I didn't get the point. First you said "technical obstacle"...in my mind, obstacles must be leapt over, bypassed, or conquered. Then you said "technical problem"..problems are meant to be solved.

I initially tried to ask you what changesets to 3.50 were made that prevent you from being able to add the same functionality to 3.40 version of the plugin. In my mind, I do not see why I cannot implement whatever changes were made in 3.50 into my 3.40 version, which would then make it compatible with your newer version plugin...but you did not answer it.

Hi Joster,

I don't know how to explain this to you either "technical issue", "problem" or whatever you would like to call it. The problem is that there are some incompatibility issues that cause the code to throw exceptions in some scenarios which are beyond our control. As you know we depend on nopCommerce as we create plugins for it and we don't have full control over the web site's configuration. nopCommerce itself is based on ASP.NET hosted in IIS and we can't make any changes to the IIS server configuration nor we can't expect our customers to do so. 
Anyway the good news is that we decided to make these changes for you in nopCommerce 3.4.
But you must know that there is a known issue if you are using IISExpress and you have your trace logging enabled (which is enabled by default). There are no problems on IIS server, which is used to host nopCommerce, so it won't affect any site in production. But in some cases this may not work on IISExpress. Of course it can easily be fixed if you disable the Trace logging in IISExress, which can only improve the performance. If you ever see this error during development "Unable to cast object of type 'System.Web.Hosting.SimpleWorkerRequest' to type 'System.Web.Hosting.IIS7WorkerRequest'" then let us know and we will tell you how to fix it on your local machine.
The bad news is that you need to renew your license in order to get the latest version of the plugin for 3.4. This is how our licensing works and all updates after the license has expired are not going into your package.

Hi! how can I do this in 3.60? 

Hi jakubz,

All you need to do is explained in this post.