I don't see any more sort by (best match etc) or page numbers It's gone and I have no idea why or how I have checked all .xml files they are all correct it's not the issue. What can I check more to fix this? Html files also seem fine I have reindex all nothing!
So you have disabled layered navigation module in admin area. It's not the real "disable", but disable of the module output. All module blocks becomes "hidden". The module rewrites the toolbar block with the sorter and pager, so it also has became invisible.
To restore the block display please enable modules output back.
If you have questions regarding the module, please contact us via support, as this site denies discussion of paid modules.
Related
Recently we noticed that our module assignment tab is missing and we cannot assign any items to some modules, example: prntscr.com/8obd8u
Here is snapshot from our previous website (to compare with the current one): prntscr.com/8obdep
Does anyone have any idea what we should check? We disabled all the plugins / one by one to check if it's going to help us, still nothing.
Also, all the pages have a Custom HTML modue. See : prntscr.com/8od9rw
So everything on the page above with a Custom HTML module doesn't have that "Module Assignment"...
Have you tried using web inspector on the problem pages to check the HTML? Maybe the missing tabs are there but there's conflicting CSS from some source which is hiding the tab list items.
You could also try changing the admin template to Hathor and see if that changes anything ... wouldn't solve the problem but might provide some clues.
Good luck!
We have a Magento site running on version 1.7.0 on the Argento theme that seems to be having intermittent issues with products not appearing. This appears to happen on certain pages and not others.
For example, if you add a product from the homepage or single category pages, it will show immediately as being part of the cart (note, Argento uses AjaxPro for the cart). However, once you navigate to another page, say "My Cart" or "Checkout" the total will show as zero. Doing a hard-refresh on the browser will update the total.
Additionally, if you open the Chrome Dev tools, navigate to "Network" and then check "disable cache" everything runs perfectly.
Things we have tried to resolve this:
Flushing/Clearing/Disabling the Magento cache. Seems to make things slightly better but doesn't clear up the issue.
x-cache-control meta tag. Same as above, issue seems to be less frequent but still definitely appearing.
Turn off AjaxPro. Our initial belief was that this plugin was causing issues, but turning it off has no effect.
Re-Index. Has no effect.
Added $.ajaxSetup({"cache" : false}) at the top of our scripts. This also has no effect.
Any advice or tips on where to look next would be appreciated.
It turns out that our hosting provider had set up the installation with the sessions stored in memcache. We switched this over to file storage in our local.xml and it fixed the issue.
I have created a custom mini-header & mini-footer phtml file that I use within a Magento installation but only on the checkout pages. (These are basically very minimal header/footers with very little content)
e.g
IF (any CHECKOUT page)
Use mini-header & mini-footer
ELSE
Use the default header/footer files for that theme.
I have a CMS static block called 'Footer Links' that will sometimes seem to override my own 'mini-footer.phtml' - it is inconsistent, sometimes on a checkout page I will see my mini-footer and another times it obvious that the 'Footer Links' static block is appearing (with 15+ html links).
At the moment the only I way I can force Magento to use my custom mini-footer.phtml is to DISABLE the 'Blocks HTML output' Cache Storage Management within the Magento Admin, however I want to have this option ideally turned on for a live site for extra speed performance.
Can anyone suggest what to do?
File this one under Works as Designed, although your question is a little unclear. Using stateful information within a cached block or the template of a cached block will lead to one state being added to the cache, and your conditional won't run again until the cache expires the entry.
As for a solution, it's not 100% clear from your question how you've set this up. You say you have a
mini-header.phtml
mini-footer.phtml
Then you have some conditional logic, but you don't mention where this conditional logic is.
Then you say you have a CMS static block called Footer Links.
You don't mention how mini-header.phtml or mini-footer.phtml are added to your layout.
You don't mention how you're adding the CMS static block.
All these details will matter if you want to find a solution to your question.
I have the same issue here. After installing a theme extension, I have come to notice that things go haywire when I click on a category: Static blocks appear in random locations. To sum it up, I got better results by disabling "Blocks HTML Output" cache.
I am tempted to try to install a different cache implementation.
My theme designer mentioned to me that this is a well known bug and that patching would help solve the problem. Although I was not able to solve the problem with a patch, I was able to solve the problem by upgrading C.E. from 1.9.2.0 to 1.9.2.1
This is my first project on website development using Joomla. I am trying to make a dashboard implementation. My problem is that whenever I edit my script in article using source tags, the changes are not reflected on my site immediately. I have even tried restarting my Wamp server, but in vain. Any tips that I should follow?
Thanks.
Depending on your Joomla-Version there are different options to check to suppress stripping or filtering of tags like <script> for the frontend. Here are some hints:
First of all your tags could be filtered out client-sided depending on the editor you selected. If you use the standard TinyMCE e.g. go to Extensions - Plugins - TinyMCE where you will find a list of prohibited Elements which may include script. Be exactly sure what you do though, always check who should be allowed to enter script tags in an article, this is almost always a major security risk if anybody else like you as an administrator has the right to use them. So another option could be to just set the editor for your administrator/author accout to plain text and leave TinyMCE untouched.
Another filtering is done server-sided by joomla itself which can be controlled in "Global Configuration" -> "Text filter". After a standard installation all groups will use Default Black List filtering which includes removing script tags. Here you could define "No Filtering" for the Super User group e.g.
Again, all this depends on your Joomla-Version (my examples are referring to 2.5) and are hints to get around the issue but without knowing your security concept.
I am having a problem displaying custom options on the product page in Magento. I'm using Modern as the base for my theme, and changing themes doesn't seem to have any effect. The catalog.xml is almost the stock one for the theme.
When viewing the page, I get the message "Please specify the product's required option(s)." but nothing shows up. Additional information that have been added to the attributes show, but no product specific custom options.
Looking with developer hints, I see that /catalog/product/view/options/wrapper.phtml is not appearing on the file. Could something be missing in one of the layout .xml files?
Any idea what might be going on? Thanks!
If you have tried enabling the default template and it still doesn't work, try creating a new product with some options and see if that works. If that still doesn't work, enable the logs and pop them open and see if there are any errors being recorded during rendering. Also, make sure that they aren't just being hidden using CSS or JavaScript (try turning off the latter, for the former use Firebug to inspect the page)
The problem I had was related to this: http://sourceforge.net/projects/magmi/forums/forum/1228365/topic/4978977
The difference is that the attribute was set to container2 in my case when I need it set to container1.
Hope this helps someone else with this issue.
Compare your layout files to the default Magento layout files.