Close
Avatar

User posts

That's what I was looking for.  Awesome!

Whoops - Wrong URL.  Here's the image:

https://docs.google.com/file/d/0BxSwbWwuTCU1cFVVVDhfdXlEZmM

No, I probably wasn't clear enough in my initial description but I don't believe that's correct.  See the following image:

https://drive.google.com/?authuser=0#folders/0BxSwbWwuTCU1Q212ZDItQUViVHc

What Im trying to accomplish (and achieved with the hard-code listed above) is to control the number of top level category columns with images.  The field you have specified only controls the category items displayed within each top level category.

I would love this feature to be in the plugin settings as I have to update this in quite a few builds.  It appears the change made in 3.4 switched this to a variable, but it doesn't appear that this variable is set in the plugin settings?

Maybe I'm missing something.  Is there something else I can do to effect this without a hard-code?  If not, whats the point of variable?

FWIW - The new view has the following line:

    @(Html.DataTable<SevenSpikes.Nop.Plugins.MegaMenu.Models.MegaMenuCategoryModel>(categoriesModels, megaMenuSettings.NumberOfCategoriesPerRow, "row", "box",
    @<text>

... so I replaced "megaMenuSettings.NumberOfCategoriesPerRow" with "3" and this worked.  My issue is resolved however Im curious if this hard-coding is no longer required?  Is there somewhere else I can set this variable so I dont have to change the view anymore going fwd?

Ive upgraded my site from 3.3 to 3.4 and I noticed an issue.  In the previous build (based on your advice) I had updated my Mega Menu to display 3 columns instead of 4 via the following change in CategoryMenuTemplate.WithPictures.cshtml:

<!-- CHANGED FROM 4 ROWS to 3 HERE -->

@(Html.DataTable<SevenSpikes.Nop.Plugins.MegaMenu.Models.MegaMenuCategoryModel>(Model.CategoriesModels, 3, "row", "box",

However in the 3.4 version of CategoryMenuTemplate.WithPictures.cshtml this code has changed and this is not where the rows value is set.  How do I change from 4 columns to 3 with the new cshtml?

Thanks!

Bugs
9 years ago

hristo wrote:
Then obviously there is a problem on your end, because it seems you are seeing a major difference. There are custom fonts in almost all out themes and the difference in font rendering is very minor, definitely not a problem.


This response seems oddly defensive to me?  I clearly stated that it was NOT a major difference, but rather that it was a noticeable.  This only matters because its presenting itself in the main menus and on the homepage which is the most visible text on the site.

This image below is snipped from your demo.  Do these differences pictured fall into what you would consider "acceptable" rendering, or do you think there's something else going on here?

https://docs.google.com/file/d/0BxSwbWwuTCU1ZFg4UVc0clVLZjQ/edit

FWIW - I use many of your templates for my customer sites and this is the first theme I recall having this issue.

Thanks

Bugs
9 years ago

hristo wrote:
custom fonts rendering is always a tiny bit different in Chrome, the characters appear a little more thick and blurry, but the difference should be really small, if you are seeing a serious difference, then there is something else on your end.


Well yes, but blurry (pixelated is how I would describe it) fonts in something as important as the main menus is a pretty bad thing.  Its not a huge thing, but its certainly noticeable immediately and looks unprofessional.

Is there any workaround for this?  If not, going fwd I would strongly suggest avoiding custom fonts on your end.

Bugs
9 years ago

Not sure Id call this a bug per se, but the 'eurostyle' font you are using for the menus looks slightly off in Chrome.  I see the same thing in your demo.  It looks fine in the other browsers Ive tested.

a)  Do you see this as well or do you think its something on my end?
b)  If you do see it, anything you can do about this?

.header-menu > ul > li > a, .header-menu > ul > li > span {
    font: normal 14px 'eurostile';
    cursor: pointer;
}

Bugs
9 years ago

If the user clicks on the search icon without entering any search text, the site should simply display a message and put the cursor in the search edit (clearing the default "search store" text).  Instead it displays the message, but then actually performs the search using the "Search store" text as the actual search text.

See the following video for better explanation:  http://screencast.com/t/zLkpD09Io

This ends up being confusing for our customers (especially those that try to search on just a category or price range).  If you could please fix this in 3.3 along with 3.4 Id appreciate it.

9 years ago

Boyko wrote:

Alternatively you can put this script into a file on the server and simply import it.
This way you only need to make sure the file is uploaded on the server after an upgrade (or update) to the site.


Boyko - Can you elaborate on this.  Obviously I understand putting the script in a file, but what method specifically do you mean when you say to "simply import it."  Are you implying this can be done thru HTML widgets, via altering the CSHTML file, or thru other means.  

Again, my goal here is to allow our customers to maintain these scripts themselves without us needing to get involved.  That was the whole benefit of using HTML Widgets in the first place.

Thanks!