I've installed SUPEE 6788 and from default, admin routing compatibility is "Enabled", all extensions work fine. However, when I "Disable" it, My Manage Products page is not working.
Does anyone know where this may be due to? Meaby I need also the update Magento to 1.9.2.2.?
Log out and login again and check if it works..
if not then check the status of SUPEE6788 in Magento Connect Manager.
One of your extensions is probably not compatible with the new patch. This is a comprehensive description of what the patch does and included is a link to extensions that are and aren't compatible with the patch. Hopefully there'll be an upgrade that will resolve your issue.
https://magento.stackexchange.com/questions/87214/how-to-check-which-modules-are-affected-by-security-patch-supee-6788
Related
I can see this error message on Drupal admin panel.
There is a security update available for your version of Drupal. To
ensure the security of your server, you should update immediately! See
the available updates page for more information and to install your
missing updates. There are security updates available for one or more
of your modules or themes. To ensure the security of your server, you
should update immediately! See the available updates page for more
information and to install your missing updates.
I tried to no display error message on this page,
Home » Administration » Configuration » Development
But I see this error message now.
Is this a version update issue? It enables, please help me. Thanks
The message is shown by the update module. For what I know there are no configuration to disable this message. It is shown just for the users with the administer site configuration permission.
I think the only solution is to disable the update module.
If you use drush you can do:
drush pm-disable -y update
Usually in the development enviroment I keep enable the update module and I disable it in the production enviroment.
You should update Drupal and/or your installed insecure modules instead of trying to "hide" the message.
Check available security updates with drush: drush pm-updatestatus --security-only
After start Crafter CMS Authoring mode successfully, I create a new site as instructed at Crafter CMS Your First Website, but the results are not the same as the description of the tutorial, all pages have status "Deleted". See the screenshot here.
Please let me know what's wrong and how to solve it. Thanks.
It's difficult to know what the issue is here because there is no log file (link does not work) but I do notice on the image a couple of things:
Everything is showing a deleted status, typically if the item is NOT in the repository it does not show at all. The deleted status typically shows up on historical dashboards.
Everything is lower cased/filename rather than internal name from the file
Hieu:
Anything you can tell us like:
OS version
Java version
Steps you took / how to reproduce
Other servers running for anything else?
I believe the correct answer to this is that there is an error in the Windows binary. I tried installing on 3 different Windows machines and had the same issue as the original poster. Plus the OP stated that the Linux distribution worked for them. I hope the Crafter people will look at this and make the correction.
I am new in magneto. my store var 1.7.0.2 need to update security patch(UPEE-6285).
I read many link without with ssl or without ssl install. but can't go with any one because i can't get backup my project and i want to go for easy steps can any one tell me easy steps for update security patch in magneto. I don't know what is ssh and how it run.
Please help me
Thanks
To learn how to install a patch check this link out: https://info2.magento.com/rs/magentoenterprise/images/Installing-a-Patch-for-Magento-Community-Edition.pdf
Easy way:
First create a backup then use Magento connect and upgrade your store to the latest Magento version by check for upgrades button. The latest version contains this security patch (SUPEE 6285) and another features all together.
update:
Upgrade using Magento connect on production server is not recommended, because you have to check extensions compatibility.
Following is my addition to portal-ext.properties for setting up ImageMagick with Liferay
I have installed ImageMagick in D drive as mention below :
imagemagick.global.search.path=D:\\ImageMagick-6.8.3-Q16
imagemagick.enabled=true
preview functionality:
dl.file.entry.preview.enabled=true
dl.file.entry.thumbnail.enabled=true
Set this to true to enable conversion and previewing of videos in the Document Library portlet:
xuggler.enabled=true
In Server Administration--->External servics tab, I have configured it correctly and also downloaded/install jar related to Xuggler.
However, above settings are not working for me to generate preview functionality.
I am not even getting message dispalyed like "Generating preview require few more time, please refresh the page after some time....blah blah blah...."
Any help is appreciated.
Thanks.
Have you configured Xuggler properly? Do you get an UnsatisfiedLinkError exception?
See Xuggler's FAQ for the steps to configure your path properly
If it shows that message "Generating preview...", seems that Liferay doesn't detect this file as a video file (the Mime Type isn't any of the values in the property: dl.file.entry.preview.video.mime.types).
I also saw this problem when uploading videos using some browsers. Try uploading using another one.
For me, the solution was to symlink /usr/bin/convert to /usr/local/bin/convert
Whatever I did, nothing seemed to work. All configuration was pointing to /usr/bin (both control panel and portal-ext.properties). As a last resort, not really believing that it will work, I just did the symlink, as that was the default location for liferay.
And it works! All my configuration still points to /usr/bin. So... it looks like liferay just ignores all that config and only looks to default folder.
I'm using Ubuntu 12.04, imagemagick from package manager. Liferay 6.1.2 GA3.
I hope it helps someone.
The following issue just crept up on me. The steps mentioned below had worked just fine until about 2 days ago.
When I deploy a update to a solution (of web parts) to a SharePoint 2010 server I don't see the update. The solution does get installed, but from what I can tell the installed web parts are over a month old (nothing new is installed).
I do the following steps through PowerShell:
retract the solution from the web app
remove the solution
add the solution
install the solution to the web app
I have tried restarting the Web App, restarting IIS and also restarting the server. Nothing seems to work.
I notice that after I remove the solution it does get removed from the GAC. After I add/install it the solution does reappears in the GAC.
Am I missing something? Am I overlooking a step that I should be doing? Something to try?
I never deactivated/reactivated the Feature.
After following the same steps I mentioned in my question I just deactivated, then reactivated, the Feature and everything started to working fine.
This is an easy thing to I can start to implement with my solution updates. However, why did I never have to do this step before?
In general, you should check your ULS log to see which version of your solution is running. If you see the old one, then you can be sure that your activated site feature is still bound to the old version. In this case you have to Inactivate the site feature indeed to loose that tie and then Activate to bind to the new one (it appears Activate always ties the site feature to the newest version of the solution).
Maybe you had not to do this earlier, because you did not change the version number of your solution, appearing as the same version in GAC on the server. In this case you had your site feature already pointing to the correct version of your solution, therefore didn't have to reset the feature.
You have probably checked, but just in case. Make sure that the powershell script is not adding a month old package.
Is the problem in the web part code or the configuration? The configuration usually unghosts itself sooner or later and refuses to update from the solution - you can update the file in the gallery manually if anything has changed there. For most updates there won't be any changes because existing web parts won't get updates applied anyway - they will use new code but old configuration.
If the problem is the code itself, does the assembly appear to the system to be unchanged? All the hardcoded full name references in SharePoint config files mean that usually you are deploying a new assembly but with the same version numbers. This can mean that the system doesn't bother making the update. I have found it very useful to update AssemblyFileVersion (which does not affect binding) on every build and have a page in _layouts that displays the file versions of all the loaded assemblies so I know exactly what is running.