Corrections in the doc markdown files.

This commit is contained in:
alext 2018-02-28 14:44:18 +01:00
parent ca6c62578f
commit 59c0d7c671
4 changed files with 6 additions and 5 deletions

View file

@ -41,3 +41,4 @@ class Config {
*This document applies to Easy!Appointments v1.3.0.*
[Back](readme.md)

View file

@ -1,16 +1,16 @@
#FAQ
##How do I check that my server has Apache, Php and MySQL already installed?
## How do I check that my server has Apache, Php and MySQL already installed?
Easy!Appointments is a php application and needs an apache server with php and mysql installed. Apart from that, the php "curl" extension and the apache module "mod_rewrite" need to be enabled. To check if your server fullfils the needed prerequisites you will need to either contact the web hosting company or create a php file on your web root directory with the content <?php phpinfo(); ?> and then access it from the web (eg "phpinfo.php" >> "http://domain-name.com/phpinfo.php"). This url will display all the server details.
##How do I create a Google Calendar API key?
## How do I create a Google Calendar API key?
Google needs to authorize the usage of her services, so you need to create an API key for your Easy!Appointments installation. In order to do that you will need a google account. When logged in, go to the Google Developers Console and create a new project. Enable the Calendar API service and then head to the "APIs & Auth >> Credentials" menu item. There, you will need to create a new OAuth client id. The last step is to enter a valid redirect url for the authrorization process. This is very important because if the redirect url is wrong, you will not be able to use the google synchronization feature on your E!A installation. For your redirect url enter the following value: "http://domain-name/folder-to-ea-installation/google/oauth_callback" (replace the domain name and the path to the Easy!Appointments installation folder with your server values). For example if E!A is installed on the "ea" folder on the web root directory the valid redirect url would be "http://my-domain/ea/google/callback".
I##nstallation Page Is Not Working
## Installation Page Is Not Working
Various users have reported on the support group that they cannot complete the installation successfully. This is primarily because of two reasons (a) either the configuration.php file was set incorrectly, or the server settings won't allow AJAX calls to be completed successfully and thus let the installation finish. For the first situation you will have to check that you have properly set the $base_url parameter to "http://url-to-ea-folder/" (last slash is necessary!), for example "http://easyappointments.org/ea-installation/". Then ensure that your database connection credentials is correct. In the second situation the things are more complex. Users have stated that in some web hosts you need to change the .htaccess file in order for the application to work (htacces snippet provided below). If this doesn't work then check the apache error log and open the browser javascript console after you press the "Install E!A" button. There you will find information about what is going wrong with your installation. Contact your hosting company and ask them to resolve these issues.

View file

@ -7,7 +7,7 @@ Welcome to the documentation pages of Easy!Appointments. Navigate through the av
- [Manage Translations](manage-translations.md)
- [Google Calendar Sync](google-calendar-sync.md)
- [REST API](rest-api.md)
- [Get Involved!](get-involved.md)
- [Docker](docker.md)
- [FAQ](faq.md)
*This document applies to Easy!Appointments v1.3.0.*

View file

@ -2,7 +2,7 @@
## Introduction
As of Easy!Appointments v1.2 a flexible REST API is integrated within the project that will make it possible to handle all the information of your installations from external clients. The API is using JSON as it's transaction format and features many great practices in order to make the resources easily consumable.
Easy!Appointments exposes a flexible REST API that will enables you to handle all the information of your installations through HTTP requests. The API is using JSON as its data transaction format and features many best practices in order to make the resources easily consumable.
## Making Requests