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.
Related
I have been working for a few days now making a simple web page to be a basic cv/bio. I started by making my headers for the page and some simple animations when switching window sizes. After playing with adding some different colors in, I noticed that an asset I added, wasn't transparent(as I had intended it to be).
That said, I have tried to delete the item from the assets Library to no avail. I've tried removing all relevant keyframes, as well as trying to delete it from the Master Rules. The program will not allow me to delete the item, except from the Library, which does not affect the item on the page whatsoever.
I may well be missing something completely obvious and shall feel a fool when this is answered. Thank you for your help in advance!
To delete a layer, click on it in the timeline so that it's highlighted and then press the Delete key on your keyboard.
If the element is an asset imported by you, for example a picture, you must select it at the library collapsible menu and click the trash. If you can't find this menu, clic on Menu > Window > Library.
On Responsive window, click Edit base document. You can now delete it.
Per user feedback, I am opening a new question for this topic.
So I am currently using Struts-Menu to handle my menu needs for my Struts 2 J2EE application. It is not necessarily a package I wish to work with I have found by playing around with it. So what are some alternatives to this package? I immediately flocked to Struts-Menu because I saw a fair amount of web search traffic pointing to it, including those who use Struts2. What I am worried about is difficulty in the future of making it work with other packages, given its 2007 last update and the extra tap dance I had do to make it work with my configuration. It seems too fragile at this point for my taste.
I have several different menus in my app, but the one I am specifically addressing at the present is like this ... The top level menu drops down upon mouse hover over it. The submenus expand horizontally upon mouse hover. Exactly one menu item can be selected as no radio buttons or check boxes are contained in the menu. This particular menu does not require db access to populate its children. It works sort of like Velocity CoolMenus4 from the Struts-Menu demos.
I've never used struts-menu, but it looks like overkill to me.
I would recommend that you locate a menu that you like and then write a tag file to handle outputting it in your view layer. To me, that's a lot easier than using a framework or library just to output a menu. Plus, its specific to the actual menu you want to use. Your tag can handle doing security checks to ensure that the user only sees what they have permission to access, etc.
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 am coding in Dreamweaver for a change. Is there a way to place reminders in your code, for example in the form of a "todo list"?
I know Eclipse has this option. You can place //TODO before the line of code and the marker is placed in a list. You can view this list at will and conveniently go back to the exact spot later.
After weeks of coding I sometimes forget to take care of certain things. A todo list in the code itself would really help out, anyone know of a method for this in Dreamweaver?
Dreamweaver doesn't have a dedicated interface for viewing TODO items. However, it does have what it calls Design Notes. These notes are stored in *.mno files that are within _notes folders within the folder of the file that has a design note attached to it. These files and folders are only viewable within Dreamweaver if you have Show Hidden files enabled, which you can do by accessing the Files panel options menu on the upper right by clicking on it, then selecting View -> Show hidden files.
You have to turn them on in the site definition, although by default, a Dreamweaver site will have them turned on. The following steps are for Dreamweaver CS4:
Site -> Manage Sites..., Select the site, click Edit, select the Design notes category, check maintain design notes. Next go to the File View Columns category and make sure that the Notes column is displayed. Click OK then Done.
You can also opt to share these design notes, which means the they will be uploaded when you FTP the files to the remote site, so that others that you work with when they download the file (and assuming they also have Design notes enabled and shared), then they will be able to see that a file has a design note associated with it. Note: These *.mno files are plain text and if you your server may be accessible by others, so be sure not to put anything confidential in them.
In the Files panel, right-click on a file that you want to add a TODO item to, select "Design Notes...". In the interface that opens, you can enter in a free form note for the document. Check the Show when file is opened to cause this interface to open when you open up the file you're applying the design note to.
If you switch to the All Info tab, you can add "keyed" notes, that is a note with a name, and an associated value. This open may be good for TODO items.
When you add a design note to a file and you have the Notes column displayed, you should see an icon in the Notes column for any files that have associated notes for. Double clicking this icon will open up the Design Notes UI. This will be a quick way to determine if you have any TODOs in the files that you can see. Note: you won't see this icon for files within folders that are closed.
If you would like to do some searches or listing of files with design notes associated with them, then you can take a look at the Site Reports Design Notes report. Go to Window -> Results -> Site Reports. In the upper right of this panel, click the green arrow. This brings up the Reports interface. Select the appropriate option under Report on, and then check "Design Notes" under Workflow. Don't bother with the report settings....it's supposed to allow for some search/filtering, but I can't get it not to display all files with notes associated with them, perhaps you'll have better luck. Click the Run button and the Site Reports panel should contain a list of files that have design notes associated with them, as well as the design note info for the file. If you double click the entry, then the file will open.
Well, i use to put a simply comment like this below, directly in the php code:
//TODO: something to do here.
When i need to check my todo list, just search in the site by "//TODO:", and voilá, this is my todo list! It works, it's free and well according with KISS requirements.
Try using doxygen to document your code.
anything marks with a #todo, will be put in a special page when you generate documentaion.
Not ideal but the best i can think of.
(I haven't had much experience with dream weaver - it might have the feature you are looking for IDK)
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.