I installed the module "algolia" in my magento store however the products do not appear as suggestions when performing a search.
The module already installed and configured correctly and even folders already has read written permission.
Every time I start typing a word in the search box my Algolia control panel shows the error 403 (forbidden) for the POST request, I need to configure any permission in my database?
Related
I am trying to upgrade Joomla from 2.5 to 3 but update button is not showing on administrator panel. It is showing “Joomla! is up-to-date”. How will I get update button. Following errors came when I try to troubleshoot.
I am not able to get response from update.joomla.org. Is it due to proxy applied on my connection. If yes then could you please let me know the step to overcome this issue.
When I get in touch to our technical support team then they provide me proxy URL with port number. Without any credential. And they told me that I have to surpass this URL after using the proxy URL. But I am not sure how I can use this proxy to get response. Please suggest and let me know the solution. Thank you!!
Errors :
Update: :Collection: Could not open http:///update.joomla.org/core/sts/list_sts.xml ;
Update: :Collection: Could not open http:///update.joomla.org/core/jed/list.xml
Within the administrator area navigate to the 'Joomla! Updater' component (under Components) - when there click on the 'Options' button in the top right of the screen. When the pop-up appears, change the 'Update server' to 'Short Term Support' and click the 'Save & Close' button within the pop-up. Once closed, the updater component should go off and check for the latest version on the 'Short Term Support' branch. The text that said 'Joomla is up to date' should be replaced with the option to install the 3.5.1 version.
Make sure you take a backup before updating. Your template and other extensions may not be compatible with the 3.5.x branch so it's best to either make sure that they are compatible or find an alternative solution.
For others that might have been scouring the internet to solve this problem, I had the same thing happening to me on a very old site that needed to be upgraded. I had an early 2.5 site which I managed to update to 2.5.28, but could not get any further due to these errors.
Most posts on this that you'll find will refer to the https version of the error, but in my case I had the same problem is the OP, where the file that could not be opened was on the http URL.
Trying to directly load the http site seemed to work, until I noticed that my browser was automatically redirecting to the https site. I don't know if that was the browser, or a server redirect causing this, but it let me to another solution to this problem, which is that these resources obviously are no longer hosted on an insecure site.
Open up the administrator/components/com_joomlaupdate/models/default.php file and around lines 37-47, modify the listed URLs from http to https. Then rerun the purge/udpate check cycle and you should now get the update found.
In addition to this, other sites that are listed as not being found on http links can be updated by modifying records in the #__update_sites table. YMMV with these, as most of them are going to be 3rd party sites that may/may not have changed hosting. In my case, most of them had just disappeared. Notably, the core update site is listed in this table, but it gets overwritten by the aforementioned script, so updating the DB doesn't help.
When I try to access two of my client's categories I get a "403 Forbidden" message. I searched SO and Joomla!'s official forums for an answer but so far I couldn't find anything related to the front end, only to some admin functions. I downloaded the site and the pages that weren't working on the server are working ok on my localhost. If I go to Directory Permissions in Joomla!'s backend it displays a red box saying "Unwritable" next to the Log and Temp directories. Checked on my host and they both have 755. What access should they have? Could it be some other problem?
Edit:
I managed to make those folders writable, apparently the problem was in the configuration.php script.
public $log_path = '../logs';
public $tmp_path = '../tmp';
This was the correct way they should haved been written. This still doesn't fix my problem so any help is still appreciated.
Thank you :)
I can't offer a solution sadly but I have the same problem. I've searched for days for a solution and am at a loss. I upgraded to Joomla 3.4.0 although problem existed before the upgrade.
Mine only happens when attempting to edit certain articles from the front-end. I've checked ACL and User has Publisher privileges and can successfully edit some pages but others cause 403 Forbidden after attempting to save changes even though they have the same category.
I tried replacing the article with a duplicate and gave it a different alias but it still wouldn't allow edits.
Have you checked the content > category manager > permissions for that user group on the problem category?
After i upgraded the magento from 1.7 to 1.9,
I am not able to access manage customer section from admin dashboard.
I am getting following error.
Gateway Time-out
The gateway did not receive a timely response from the upstream server
or application.
Edit:
If i clear the cache it works for the first time and then the issue will reappear if i try to access the manage customer section again.
check your installed extensions if you find any extension for manage customer then disable it and check after refresh cache.
This error generally comes when one server waits for response from another server for too much time. But it could be anything. What I would suggest you to check the Mage_Customer module and if it is enable try to remove log of the website as it make website slow. For removing the log try this
login to shell(SSH) panel and go to your website root/shell folder.
execute the below command inside the shell folder
php -f log.php clean
I recently updated all of my features in Magento from 1.8 to 1.8.1 and after that I’m having problems to log in to the admin dashboard. If i go to “www.example.com/admin” i get a 500 Internal Server Error error and was googling around i wasn’t able to find a solution.
Then i noticed i can go to “www.example.com/index.php/admin” and then all it returns is a blank page. And after hosting the log in page locally sending the right information to the original hosting service i get logged in, but the dashboard is totally blank.
I’ve tried all of the mighty google advises I’ve found, for example, clearing catch, changing permission to folders, looking in log-files for solutions, changing in the .htaccess, etc. But still haven’t found out what the problem is. Anyone had the same problem and maybe has a solution or advice?
Thanks in advance!
I am trying to setup multiple stores within same hosting account and I studied many interesting guides out there on the matter.
Seems to me I figured out simplest solution for me - map both my dot com sites onto the same directory on host, and modify .htaccess to launch different website depending on URL, like so:
SetEnvIf Host .*anatscraftonia.* MAGE_RUN_CODE="anatscraftonia";
SetEnvIf Host .*anatscraftonia.* MAGE_RUN_TYPE="website";
My first store works fine, but when I go to anatscraftonia.com , all I get always is a Magento 404 page.
I checked all settings, multiple stores are defined and code above is copy/paste from Admin console under Website I added. I have Home page enabled for All Stores and Base URL redefined for both Secure/Unsecure. I also tried changing website to store, with no improvements.
What else am I missing? How do I even know what page is it trying to go to, or whether it even gets “no-route” or just totally whacked…
I threw together some quick and dirty code a few years ago to log the controller dispatch process in Magento Community 1.3x.
http://alanstorm.com/magento_controller_dispatch_logging
I don't think you'll be able to drop those files into a current installation, but it should give you an idea where to stick some logging functions to see why Magento is routing to a 404.
I am not 100% sure what you are trying to achieve but why not use a single instance of magento to handle both stores and magentos own multi store capability..
full details here http://dx3webs.com/front/2010/08/magento-multistore-setup-under-plesk/ post contains links to cpanel instructions as well.
the instructions are for multiple domains but will work with sub folders