I am attempting to set up Magento on my Dev Server, but I can't get the URL to work.
I have a copy of the live version, which I installed. I then updated the config.xml file, emptied the cache folder (var/cache) and updated core_config_data with the new URL, but for some reason I am still getting redirected to the live URL rather than the Dev URL which I just configured.
Any ideas or help would be greatly appreciated.
If non of the other answers here, about ensuring ALL the values are set correctly in the database, are correct, it might be that the var/cache directory wasn't writable. In which case you would need to clear your cache in the system temp directory (/tmp/magento/ on most *nix based systems).
As an alternative, check your .htaccess file and ensure your live domain isn't referred to at all (RedirectRules, Redirect etc.).
In Your Development Server Database has the Live Server Url.
Just find and replace the Live server Url with Development Server Url in Dev server Database.
Example:
Live Server :
http://live-server.com
Development server :
http://dev-server.com
You Just Find the http://live-server.com in Development server Database And replace with http://dev-server.com.
It would be helpful to you.
Did you try clearing the session folder?
Go to phpmyadmin, execute this query and correct found values.
SELECT * FROM (SELECT * FROM `core_config_data` WHERE path LIKE "%url%") AS A
If you go to the database, look for core_config_data table. You need to change the value of web/unsecure/base_url and web/secure/base_url to your dev server url.
You may need to clear the cache on ./var/cache
Oops. :) I found my own issue...
Apparently I had a copy of the live file in app/etc/local.xml as backup_local.xml
However, the application loads all files which have the .xml extension - so it was loading the backup_local.xml file as well... Oops!
I hope this catch helps other users with a similar issue!
Related
I just got a typo3 website and need to transfer to an other domain.
Is it enough to copy all the folders (except typo3temp?) to the new place?
First I just changed baseurl in ts but it didn't do anything..
Should I do anything with the database when it still on the same server?
In case your question is about "cloning" a complete TYPO3-system an rsync/copy of the whole folder (yes including typo3temp) is the best idea, as this works on all versions, everything else (like excluding typo3temp) depends a whole lot on your TYPO3 expertise to resolve. The database needs to be copied as well. If you need to change db-name or db-credentials on the new system you need to change them in
typo3conf/LocalConfiguration.php
As soon as you have done this Install Tool and Backend should work: At first try the Install Tool:
https://my.new.domain/typo3/install/
If that doesn't work your problem is with the webserver configuration or dns.
If that works (and the reports there show no errors), try the Backend:
https://my.new.domain/typo3/
In case your question is about which changes are necessary to your TYPO3-installation if domain changes and the web server itself is configured correctly, then there are probably two things you need to change, in order to make the frontend work (although both cases might be omitted, depending on your configuration):
sys_template record, if any of those use absRefPrefix or baseurl. If you have access to the MySQL-Database a
SELECT pid FROM sys_template WHERE config LIKE "%baseurl%" OR "%absRefPrefix";
might help finding the template, however these template configuration might also be stored in files (typically in fileadmin/templates/**)
sys_domain records, a MySQL
SELECT pid FROM sys_domain;
might uncover where those are stored
However these changes are only necessary to enable the frontend to work.
Add a domain record in the backend. And while you don't need the content of the typo3temp folder, make sure the folder actually exists.
When you go to the new domain name in your browser, what happens?
Do you get redirected to the old domain? If so, maybe there is an .htaccess redirect happening.
Do you get to the new domain, but if you click on a link end up on the old one?
Do you get an error? If so, what is the error?
Does something else happen?
I know that the Swagger-editor saves api documentation into the local browser cache ("Download Yaml/Json" and "Export Yaml/Json").
But what if I want to save it into a remote server then latter I can continue editing it from another browser.
Are there already known Backends for Swagger-editor which I can use?
Thanks in advance.
The swagger-node project has the editor built in and saves files in your filesystem.
Follow the steps in the README to install and run. When you make changes in the editor that you launch (your browser), they are autosaved, and you can see the change in the api directory. For example, if you change the { info: { title } } key, you'll see it autosave and then you can see the change in ./api/swagger/swagger.yaml.
There is an option to useBackendForStorage: true which does a HTTP put to a backend server.
Little late to the game, but maybe helps others:
There is a very simple backend here, written in go:
https://github.com/zgiber/sweb
It runs as a http server on your localhost, and opens the editor in a browser. Saves the swagger file as you type.
Today I installed v1.9.2 on win7 64-bit server at fixed ip address 192.168.1.99
When I attempt to open the neo4j web admin, using explicit url 192.168.1.99:7474/webadmin/, I get a timeout error. However, when I replace the url with localhost:7474/webadmin/, then I connect without a problem. This is also problematic for my internal webapp as no else can access it without the server url.
Both localhost and 192.168.1.99 worked flawlessly with v1.9.RC2
Can anyone help me resolve this so that I can use the explicit url?
Can anyone recreate this to make sure I am not losing my mind?
Update: I also uncommented the line "org.neo4j.server.webserver.address=0.0.0.0" in the neo4j-server.properties file. When commented, the database only listens on localhost (only accept local connections). This had no effect.
Update2: worked on some javascript - found a bug, fixed it, and now the explicit url is working. Not sure if this is a coincidence. Regardless, hope uncommenting "org.neo4j.server.webserver.address=0.0.0.0" in the neo4j-server.properties file helps someone.
Thanks,
Jeff
I know there is a way to set your processmaker in such you can access it by using the following format:
processmaker.example.com
But is there a way to configure it in such you can access it by using:
example.com/processmaker/
Thank you and good day.
ProcessMaker is configured to respect the structure: xxx/sysworkflow/en/classic/login/login, so changing it to:
http://XXX.XXX.XXX.XXX/processmaker/
it won't work unlike wordpress that you have the possibility to create subfolders.
In the case of ProcessMaker domains or ports are created to have access. In your case you can create a rule to redirect your URL to processmaker login, it means when you enter to
XXX.XXX.XXX.XXX/processmaker/
it redirects to:
xxx/sysworkflow/en/classic/login/login
You need to modify your .htaccess file or pmos.conf file depending on how you installed ProcessMaker.
This information may help you to redirect your URL.
Regards.
processmaker
Unfortunately, ProcessMaker needs to be on the root of any server configuration. This is due to the .htaccess configuration file, which goes to sysGeneric.php.
Another problem is that the application uses full paths (e.g. /js/maborak.js) and it won't work on a folder unless you modify the templates.
One of the log files that i used regularly on my last server was the rails access.log
On our new host the file isn't supplying any data. I did a search and couldn't find any reference to the file. I'm wondering if needs to be configured and/or whether there are specific ownership/permission settings on the file that need to be in place.
Thanks for your help.
Access.log is usually written by the web server, not Rails. Check the apache or nginx or whatever config to find out where it's writing it. My guess is you're used to it being configured to be written in the same place as your rails logs, but now it isn't.