Close

Profile: joster

Avatar

User posts

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.

joster wrote:
Also...if you will merge the new token into version 3.40, was this new feature added before or after 6/12/2015? That is when my license for customer reminders expired.
The download package that I can download from my account is this:
NopCustomerReminders_3.4.1149.16357

Will I need to renew my license to get it?

Hi Joster,

Unfortunately we will not be able to add this feature in nopCommerce 3.4. There are some technical obstacles that prevent us from doing this.
I would advice you to upgrade to the latest nopCommerce 3.6 version and this way take advantage of all the new features and improvements in our plugins and the nopCommerce platform.


As I said, we will not be upgrading past 3.40, so will you please explain the "technical obstacle" to me?


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?

Boyko wrote:
Also...if you will merge the new token into version 3.40, was this new feature added before or after 6/12/2015? That is when my license for customer reminders expired.
The download package that I can download from my account is this:
NopCustomerReminders_3.4.1149.16357

Will I need to renew my license to get it?

Hi Joster,

Unfortunately we will not be able to add this feature in nopCommerce 3.4. There are some technical obstacles that prevent us from doing this.
I would advice you to upgrade to the latest nopCommerce 3.6 version and this way take advantage of all the new features and improvements in our plugins and the nopCommerce platform.


As I said, we will not be upgrading past 3.40, so will you please explain the "technical obstacle" to me?

Also...if you will merge the new token into version 3.40, was this new feature added before or after 6/12/2015? That is when my license for customer reminders expired.
The download package that I can download from my account is this:
NopCustomerReminders_3.4.1149.16357

Will I need to renew my license to get it?

hristian.dimov wrote:
We can't upgrade to 3.6 right now due to time and dependencies.
Is there anyway that this can done with 3.5 or something that at least takes them to the products?

Hi,

We merged the changes in 3.5 version. You need to download and update the plugin to the latest version following this article: http://www.nop-templates.com/how-to-update-a-nopcommerce-plugin

After updating the plugin you need to go to the \Plugins\SevenSpikes.Nop.Plugins.CustomerReminders\Views\TokenTemplates\_ProductsWithPictures.cshtml view and change this:

string productUrl = storeUrl + productSeName;


to be:

string productUrl = storeUrl + "productreviews/" + product.Id;


The new token that you should use is in the message templates is: %Order.ProductsWithPictures%

Note: Keep in mind that this will affect the AbandonedShoppingCart.ProductWithPictures token. If you want to make the change only for the CompletedOrder.ProductWithPictures you will need to copy the whole content from the _ProductsWithPictures.cshtml, paste it into Order.ProductsWithPictures.cshtml view and do the url change there.

Hope this helps!


Hello-

We will not be upgrading past version 3.40, but very much would like to be able to reference the %Order.ProductsWithPictures% token in our customer reminder message templates. 

Is it possible vor version 3.40?

Thank you!

9 years ago

OK, thanks for the explanation.

9 years ago

Hello-

We are integrating Google Site Search (Custom Search Engine) into our nopCommerce 3.40 site with the Alfresco theme.

I have it working now on our development site, but I need help understanding how the search box is displayed in two different positions on the Alfresco theme.

What I mean is, on the home page, the searchbox is aligned to the left, whereas it is aligned to the right and positioned lower in the header of all other pages.

To integrate GSS, it was necessary to replace all code on the /Views/Catalog/SearchBox.cshtml with only this code:


<div class="search-box">
<ul>
<li>
<gcse:searchbox-only resultsUrl="http://www.my.domain.name/search" queryParameterName="p"></gcse:searchbox-only>
</li>
</ul>
</div>


But now, when viewed in a browser, the searchbox is positioned the same in both home and other pages..to the right?????

So..I want to create a new class in my styles to position the searchbox differently on the home page.


I see this code at the bottom of \Themes\Alfresco\Views\Shared\_Header.cshtml:

<div class="search-box">
@Html.Action("SearchBox", "Catalog")
</div>


I understand it is where searchbox is called for header of all pages.
But, I DO NOT understand from where is it called to appear on the home page so that I can specify a different class for it's div.

Please help.

9 years ago

Hello again-

As of this week, we are now having traffic appear on our website that is accessing this URL:
http://www.myfootshop.com/producttab/productcustomtab/

Of course, this throws an error every time because no parameters are included:
The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Int32' for method 'System.Web.Mvc.ActionResult ProductCustomTab(Int32)' in 'SevenSpikes.Nop.Plugins.NopQuickTabs.Controllers.ProductTabController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter. Parameter name: parameters

This is further evidence that Google is indexing the producttabs pages as stand-alone URL's, even though they are not included in the sitemap.

Am I really the only person noticing this?

9 years ago

I'd just suggest that you utilize the built-in feature of nopcommerce to display all categories on home page, and use the menu for what it was designed...

9 years ago

Boyko wrote:

I don't think it is a good idea to block google from indexing these pages. As far as I am aware googlebot resembles the loading of the page as it is in a browser. So it is not a good idea to stop google from accessing these pages (loaded via Ajax) as they will no be indexed.
Usually google uses the sitemap to know if a page is accessible or not. In the sitemap these Ajax loaded content pages are not present, so google should ignore them as being separate pages and should not index them as regular pages.
In summary my advice is to remove the captcha and leave it as it is now.


I would have agreed with you a month ago, but now that I have learned that Google is absolutely attempting to crawl and index these tabs pages as stand-alone URL's (even though not in my sitemap), and giving bad mobile-usability reports because of them, I feel I must do something.

Thanks.