Can anyone suggest me, which file is responsible for dockbar menu changes for admin user and other user in liferay 6.2 ?
I made changes in \docroot\META-INF\custom_jsps\html\portlet\dockbar\view_user_account.jspf file for the dockbar menu,
but changes is reflect only Guest user dockbar menu.
Please suggest me file where the dockbar menu comes for admin user and
other user.
You found the correct directory - dockbar's jsps are in Liferay's html/portlet/dockbar folder, however there are 16 jsps in there and you either picked the wrong one or edited within some conditionals that only display for the guest user.
They're all overridden the way you're doing it already in your hook. Which file exactly contains the markup that you need to change you'll have to find for yourself. Same with the location in the file to change. Especially as you only state that you need to "make changes" - not sure if you add more options, change existing options, reorder, or just change the DOM.
in dockbar exist public page and private page .you can manage dockbar in portal_normal.vm .
in this vm file you acces dockbar whit #dockbar() and put condition for show or hide dockbar.
Related
I accidentally installed a more recent component of J2XML designed for Joomla 3 into my J2.5 site... and now I have no idea how to remove it. The only Admin page that works is the main Admin page... all the other admin pages are blank... I'm assuming it's logging the error somewhere, but I have no idea where that would be.
Can I manually remove the extension/module? What database tables should i remove?
I have already removed the folder of files, but I'm not familiar enough with the Joomla db structure to know what damage has been caused.
And in this case, backups have failed me.
you should able to look at _components table and remove J2XML entry so it doesn't show in administrator panel
All admin menus in Joomla 3.3.1 suddenly disappeared!
I worked at the site's user groups and adjusted a little CSS using firebug, when I suddenly lost all admin menubar, buttons / content in the subheader and content in the header
None change in the core files and no errors are shown
You can see the image....
This is not a programming issue. It's hard to know which exact change created the problem but if you are playing with user groups most likely you accidently put yourself into a group which does not have permission to see the menu module . Go to the module manager (add index.php?option=com_modules to the admin url.) and change the settings on the admin menu module to public ... then check to make sure that your user group has permission to see "special."
I installed opencart 1.5.6 on my localhost, and it's not possible for me to change the theme. The admin panel says the new theme is active, but the default theme always appears.
I made the same installation on a remote server, and everything is working well there.
I have no idea what's wrong on my localhost. I'm on a new installation on Ubuntu 12.4 with a default configuration for LAMP. I tried to compare the two phpinfo but there are so many things that are different that gives me no clue.
It was just a problem of rights on the theme folder. Very stupid ...
First, I would check your database to see if the change is registered. Use phpMyAdmin (or whatever included with your LAMP stack) and look at the "oc_setting" (prefix may differ) and see if the config_template is set to the template you've chosen via the admin. This will help identify if the issue is database related.
I have the solution, the ACTUAL solution. (For me anyway)
Extract the theme.
Login to your OpenCart website using FTP. Please read our article if
you need help using FTP.
Upload the catalog and images folders to the root of your OpenCart installation.
Once the upload is finished, log into your OpenCart Dashboard and go
to System > Settings
Choose your website from the list, check the box next to it, and select “Edit”
In the store tab you will now see your new theme option available under 'Template'
Click Save.
It has now been updated.
Many, many tutorials online at the moment incorrectly instruct people to upload their theme directly into the catalog > view > theme location as though it were a WordPress theme or similar. You actually need to put the appropriate resources where they need to be.
I have my shop showing this URL when a user checks out.
index.php?page=checkout.index&option=com_virtuemart&Itemid=65&redirected=1&Itemid=65
for all the steps it does not show the checkoout_stage as i would expect below in the URL hence it ends up using the home template with the layout distorted
What i expect instead:
index.php?page=checkout.index&option=com_virtuemart&Itemid=65&redirected=1&Itemid=65&checkout_stage=1
index.php?page=checkout.index&option=com_virtuemart&Itemid=65&redirected=1&Itemid=65&checkout_stage=2
index.php?page=checkout.index&option=com_virtuemart&Itemid=65&redirected=1&Itemid=65&checkout_stage=3
index.php?page=checkout.index&option=com_virtuemart&Itemid=65&redirected=1&Itemid=65&checkout_stage=4
One common mistake that will give you this type of problem is not having a menu item for Virtuemat or the VM module published somewhere. You have to have a menu item for VM, even if its in a hidden menu, same with the VM module. Even if you put it in a hidden position you still have to have one and it needs to be published.
If that doesn't do it, we need a lot more information before we can help.
I have recently built my first Magento extenstion.
It involves adding a new menu item in the admin area and works perfectly on my development server.
On the live server however, the menu bar item fails to display.
I am pretty sure that all the files have been copied over and I have refreshed all of the cache.
I have checked the system > configuration > advanced area and the module is listed in the disable section.
Are there any other settings/configurations I need to check?
Did you setup your menu with ACL roles? If so, does your user have the correct role?
Assuming the above is true, the Mage_Adminhtml_Block_Page_Menu class is responsible for rendering the menus. I'd start by adding some temporary debugging code to determine why this class is skipping your menu. (is it skipping it, or does it not know about it? If it doesn't know about it, why isn't your system reading it from the config) etc. etc.