Hello I am using algolia for search on my laravel project. It was working good but now when i search for content it display error. I also tried for composer update, but it is not allowing me to update. i am attaching screenshots of error when i search for content and composer update issue. Check this image
and this as well
I know its an old topic but I'm sharing my experience here. It my help others.
This issue also occurs when ALGOLIA_APP_ID is not properly set up. Usually people use wrong APP ID from algolia dashboard so make sure to use the correct APP ID as shown in the following image.
It shouldn't be taking 1 second to resolve the host, so I recommend you to check your DNS settings or your Internet connection.
But anyway, if you still want to have longer timeouts all you need to do is configure it: https://www.algolia.com/doc/api-reference/api-methods/configuring-timeouts/#methods
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.
I really stuck on this issue, everytime i log in into magento admin, it's give me an ERR_EMPTY_RESPONSE on google chrome and Connection reset on Mozilla.
The shop is still accessable, but it's load very slowly. It's working fine before, and suddenly become like this.
I can't find a similiar issue like this, mostly are the shop that return an empty response and they still can access the admin page and it's caused of enabling flat category/products set up.
I'm not sure if client enabling the flat category/products. If it so, what table should i edit using phpmyadmin?
since i can't access the admin page, or there are another thing that cause this? some error code, some files missing in admin directory or htaccess thing, actually i'm not doing changes on htaccess before. Really need your help.
Restarting apache and mysql worked for me
service httpd restart
service mysqld restart
Hope this helps.
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 have a magento install on a staging environment, everything is working except the catalog backend page and the frontend layered navigation. Look at the image below. There is a backend within the backend. When visiting the page it refreshes to infinity. See this identical problem
My first guess is there is a bug in the template file but an identical template file on my local machine does not cause any issues. Additionally the database between my local and staging site are identical minus the core_config_url. The only difference is local I am running Apache and on staging I am running nginx.
The second issue which I imagine is related is that the filters on the frontend catalog page dont work. They are visible but clicking on them reloads the page without changing the products.
Any help would be appreciated. Thanks
UPDATE: After switching from NGINX to Apache the issue disappeared. I still would like to figure out what is causing the problem
I take for granted that you had already tried different browsers/clearing your browser cache and Magento cache (empty the cache directory), etc.
Are you sure you put the correct value in the cookie_domain setting? Many users that had your same problem seem to have setted up an incorrect value in that setting.
Take a look here and let me know.
I have found that usually this is caused by a server-side error on the ajax request. If there is any kind of error response returned, it will just continue to spin. Either check your Chrome console for a 500 response, or look in your server's error logs.
This time i am having a weird problem about a Joomla 1.5 website.
When I try to add new article (number 3093) to a section/category that is in the menu and then I try to retrieve it, when i call the single article page i get an error. I can't say it's a 500 error because in my hosting logs and in joomla log i can't find any trace of the error.
Even when I curl the documents what i get is an empty response.
I checked the MYSQL databases and the article are here, i tried to recover a backup of the database and everything went ok, but when i try to add the article > 3093 i cannot retrieve them.
I tried changing themes, removing mod_rewrite, debugging php and mysql, but everything is working fine, i think that something is going wrong with the controller routing.
Anyone can help, any idea or similar experience can be appreciated