I have a problem with Prestashop. I have a second menu that I want to display on some pages.
For example, when I click on "program", I get to the "program" page but the side menu does not appear.
I know that it is possible to do this in the block configuration options.
I've tried a lot of things but nothing works, if someone has any advice / lead to give me.
I use a translator, hoping that it will be comprehensible, I remain at your disposal for any further information.
Thank you all, have a good day.
Related
I have a question about Ultimate Special Offers plugin. Has anybody used it?
The problem is that this plugin sets the table with discounts in a special place where it wants. In my case, it shows up under the "add to cart" button. But I want it to appear above the button. How can I regulate the place where the table shows up?
You have two choices. One is to dig into your theme and move the table yourself. If you right-click the element displaying the table while having your browser console open, you will spot where it is in the HTML that makes up your page. Now click the Add to cart button, and see where it is. Memorize the name of the button, and now look for that in your product.liquid page. Chances are, the plugin itself has some liquid, so you can cut it out of the page, and move it the before the add to cart button in the liquid.
If all that seems like a mountain to climb, just ask the makers of the plugin to do it for you. It is a simple task for them, and should take them a minute to do. If they choose to ignore you, I would call them out as unreliable, and try a different plugin, from a company that will help you with your simple task.
It's hard to explain by words, so I'll just provide a screen shot for it.
Is there any other way to disregard the path on main menu on drupal?
So when I just click it, it won't happen anything, just a # sign.
Hope you understand, any help would be appreciated.
Use Special Menu Items module. Drupal will not allow you to use a special character like #,?,. etc by default in menu links.
If you know the exact page you want it to lead to, you can enter the full html e.g. html://www.yourdomain.com/my_page
But, I don't understand why you would be adding a link to a menu if you don't want it to be a link?
If you want to disable menu links (e.g. "home"), go to "/admin/structure/menu/manage/main-menu" and just disable them using the check boxes next to the menu entry.
After much online research and getting close to what I am looking for by hacking it together (ie. modifying templates and other files, exactly what every expert out there appears to advise against in terms of SharePoint customization) I have decided to go ahead and post my issue here to see if anybody has ever had any experience with this.
In essence, I start off with a plain My Sites host. I would like to keep the My Profile and My Content pages, and add a bunch of new content of top on that. For us, simplicity is of utmost importance and so when I created a new Web Part Page and noticed that it added an additional ribbon under the navigation menu, I decided that it had to go. This is what it looks like out of the box:
With ribbon
Notice that at this point I have already made a few modifications, such as removing the My Site link that by default appears all the way to the left of the other options. This sadly was accomplished in a very brute-force way.
Now, here is the ribbon-free navigation bar, which is just what I want to be able to design without making system changes that I will regret in the future (and that may be easily overwritten by a CU or hotfix)
Without ribbon
So I guess I should make this clear, I don't want the navigation gone, just customized (ie. no My Site string to the left of my options, no Site Actions drop-down for read-only users) and the Browse/Page ribbon that gets added by default everytime you create a new page, well that one just needs to be gone completely, as shown in the second screenshot.
I have read all about hiding ribbons (which just hides the whole thing, including navigation), customizing ribbons (no success in accomplishing this type of basic navigation after trying them out) and simply don't know what to do anymore.
Maybe I am just taking the wrong approach by modifying something instead of just creating it from scratch, at the end of the day it is nothing but a static navigation bar common to all the pages with the special current user drop-down all the way to the right, then if a user has write permissions, she would also get the Site Actions drop-down under Home, that's it.
Hopefully an answer to this question will help others as well who are looking to simplify their SharePoint My Sites host a bit, as out of the box the number of web components that users are presented with might be just a little too overwhelming for your everyday employee, at least in the industry that we operate in.
Anyway, thank you kindly in advance, I look forward to your replies. Do let me know if there is something that is not entirely clear from my explanation :)
If you take away user's Create Personal Site permission (http://technet.microsoft.com/en-us/library/cc262500.aspx) in your User Profile, the "My Site" link will go away.
I have this strange problem on my web page where if you click below the left side-panel, all the links get highlighted. It happens in firefox, not IE. I don't know why its only the side-panel that it happens to. Its not really a big deal but its extremely annoying to me, is there any way to stop it? If you want to check it out, the site is http://www.bhslaughter.com/
Not to sound harsh, but that's a serious case of div-itis. You might want to check the number of links that you have, the open and closing of the div's, empty anchor links and the wrapping of your multiple tables.
Good luck with your project.
Well I found out what it was. I had the left side menu floated inside the table. It was a left over from before I used the table to layout the page
I was wondering if it was ever ok not to have a submit button (Ok, Go or Search for example) near a search box in Web pages.
I know that hitting enter is much faster and that it will perform the search.
However, is it an accepted convention for the average non tech savvy user or only for the tech community?
For example, the search box here at stackoverflow doesn't have a submit button, but I don't think anyone is complaining (and I sure don't).
On the other hand, someone suggested using Google as an example: would people notice if the buttons were removed?
I just started reading Don't Make Me Think by Steve Krug and he mentions that every search box should have something that tells me I can click on it to launch the search.
Your thoughts?
Why you should have a button:
Not everyone knows they can hit
enter, so you are leaving some less
savvy people out in the cold.
Some devices like phones and consoles may not have a way to submit without a button. The PC based browser is still dominant but don't assume it is the only way people access your site.
You may not have a button if (both conditions must be satisfied):
Your audience is tech savvy (as on SO)
You provide a visual cue that the search box actually is a search box
By adding text inside it mentioning it should be used to search
By adding an icon inside the box
Generally I would think that hitting enter is a shortcut to submit rather than the primary means.
I think it depends on your target market. If you are StackOverflow it's not too hard too think they know how to use a browser (using a back button on a browser to navigate is a similair design convention) and pressing Enter = submit for search.
However if your target market is say mechanics (no offence to mechanics) that don't use a browser/computer often then look at how Google does it (and they target the broadest scope) - they have a button to submit.
There is a middle ground you could look at, which is have a water mark like StackOverflow which tells users "Click here, type in search values and press enter to search" - or something like that (hopefully shorter) where you actually catering for users of all levels.
Whether or not a button is required depends on the audience. Here are issues to consider:
Technically oriented users may not need a button and will usually not have to think about hitting enter to submit a search request.
Conversely non-technical people may not even know it is possible to hit enter to submit a search request. So no amount of thinking might work for them.
There may be technology limitations that require a button. If you expect your audience to be browsing your form from a platform that does not provide an implicit way to submit a search request then you may need to provide an explicit button.
So essentially you need to know your audiences and determine where the edge cases lie and how critical they are. Using SO as an example, it is directed at technical users so an explicit button probably isn't required. However for a site like google where you need to be accessible to every single user using every possible platform, a clear explicit search button is a must.
"Don't Make Me Think" - so gimme a button.
There will always be someone using the application for the first time; don't make them think either. And your screen shouldn't be so fussy that it is impossible to fit the button in comfortably - that would indicate a different set of problems.
I think for a non-tech person some sort of submit button is needed. Think about people who don't use computers very much. They often click all of the buttons needed instead of hitting enter because they don't realize enter does the same thing. My opinion...if it isn't for tech guys only then it should be as simple as possible.
It depends on your audience. Steve's audience is everybody. Majority of which are so far from IT you'd need a telescope to see them. If your auditory is a single user, you might skip all clues: button (with or w/o names), in-box label.
For my own login window I leave two fields: no labels, no buttons, no javascript to tell you which one is which. But that's not a public project.
A while ago there was an article on Smashing Magazine about this.
There were some alternatives like a looking glass or another icon, but basically there is always a button, or something which represents it.
Having a button makes it clearer that the text field is a search field. Merely having the text field itself indicate this in its contents is unsufficient.