Profile: Boyko

Hi Damir,

Thank you for your feedback!
You are right that these could not be changed per store and we have no other choice but making them as settings. By the way you have a single domain license and in order to use the theme on more than one store you should have a multiple domains license.
The HelpDesk plugin does not have a specific styling for the Pavilion theme since it comes with styling for the DefaultClean theme and it is not shipped with the Pavilion theme by default. But we can provide styling for this plugin if you would like to use it with the Pavilion theme. Please send an email to our [email protected] mail requesting styling for the Pavilion theme.

Thanks

I am now even more confused. What plugin are you talking about?
Please let me know so that I can advise.

Hi markokrstic,

There is no such option out of the box in the administration.
Are you talking about the New Ticket page where the customer can select a product or for the product page where there is a link to the New Ticket page (i.e to hide the New Ticket link on the product page)?

Hi ScotterMonkey,

The Blog Archive functionality comes from nopCommerce by default and it is not something that our plugin changes. I think what you suggest makes sense and it will be quite useful (in my opinion) so I would suggest you to suggest your idea in the nopCommerce forum as it should be added in the default nopCommerce functionality.
Of course you can suggest it in our UserVoice portal and let others vote for it but we usually try not to change any default functionality that is built into nopCommerce but rather to build on top of it or to extend it with a new one.

Hi steefD,

As I said it will be best to submit a ticket. Your customer should have a valid license in order to get free support. Then you can simply package and attached the source code or upload it somewhere where we can get it and debug it locally.
You can check if there are any differences between your local machine plugins and the deployed version on your server and that could help you see what might be wrong. Maybe the Core plugin is not installed and you are trying to use something from the Core plugin that is not available (since it is uninstalled). Please check the InstalledPlugins.txt files on your dev and your productions environments if they are the same.

Hi Vedran,

I understand your frustration but what you say is not quite true and since I don't what you to mislead our customers reading this I will show some of the facts here.
You have submitted your initial support request 2 days ago on 19/04/2016. We have replied immediately on 19th and then on 20th we have replied 4 more times. Please note that we guarantee 24 hours response time and we have replied to you 5 times for these 24 hours. Today 21st we have replied 3 more times and we found what the problem was. I don't want to comment if this is bad or good support as I believe everyone can decide for himself.

Regarding the actual issue.

The customer complained that he doesn't see the Widget Zone in the administration of the Ajax Filters plugin, which prevent him to integrate the plugin in his website.
Initially we though the problem was related to either a missing SupportedWidgetZones.xml file or not having proper permissions, which turn out not to be the problem.
Today the customer provided FTP access and we found out the SupportedWidgetZones.xml is renamed to be with lowercase - supportedwidgetzones.xml. That is why the widget zones were not found and loaded in the administration of the plugin. So if anyone has the same problem please make sure you have not renamed the supplied files as this may have some side effects and could break the functionality of the product.

Hi Steef,

Thank you for this information but I don't see how we could help unless you provide us with access to you nopCommerce installation so that we can see what could be wrong. I am pretty sure there are some other plugin (not from the default nopCommerce plugins) that is causing this issue or you have some modifications to the code that is causing it.
Anyway if you could submit a ticket providing us access then we will be able to advise.

I would really recommend you to simply upgrade to the latest nopCommerce version as nopCommerce 2.3 was not a stable version that you should use for production websites. Since then there are many new bug fixes and improvements in nopCommerce.

Are you serious that you are using nopCommerce 2.30? This is almost 5 years old version. Even nopCommerce dropped the support for all versions prior to nopCommerce 2.65.
I would advise you to simply upgrade your website to the latest nopCommerce 3.7 version.
Anyway please let me know which of our products you are using so that I can advise. Most probably you are using some other plugin that is not compatible with our plugins which was often the case with the old versions on nopCommerce.

Hi JayC,

I agree with you but this is a Core blog functionality on which the Rich Blog plugin is built on. It is actually better to use the Start Date rather than the Creation Date.
The nopCommerce team has already created  an issue for this so you can comment on it and ask when it will be done.
https://github.com/nopSolutions/nopCommerce/issues/841

Hi myo myint han,

The theme will be released soon so then you will be able to see the demo (actually there will be 2 demos)