@Aman-deep-sharma Thank you. All fixed!

@Mimperio

If you have already installed the QloApps on any of your server and want to migrate from your old server to new server then you can refer to this document to learn how to migrate QloApps to a new server: https://qloapps.com/how-to-migrate-qloapps-to-a-new-server/

@Mimperio
Yes, As QloApps is an open-source system. So you can definitely edit the code yourself as per your requirements but only for your personal use.

However, as per our company policy, we do not allow the Reselling, whitelabeling, or any kind of rebranding of QloApps.

Also, just to inform you that if you make custom changes to the code, any issues that arise on your system by custom changes, will not be covered under QloApps' free support.

Hi @Mimperio,

I am glad that the suggested steps helped you disable the catalog mode on your website.

The catalog mode feature is used when you want to showcase your rooms and other essential information to your guests but you don't want to allow them to book the rooms on your website.

The catalog mode allows you to turn your online hotel into a catalogue, by removing all booking options from your website.

@Mimperio

As i am in France i use OVH as hosting provider , and a VPS

Hi,

As per the hotel industry standards each room should have at least one adult member to it. So in QloApps also minimum 1 Adult is required for base occupancy of the room type.

As per your requirement set the following occupancy Under the Occupancy section of a room type:

Base adults = 1, (As per hotel standards, there should be a minimum of 1 adult as a base occupancy)

Base children = 0

Maximum adults = 2

Maximum children = 2

Maximum room occupancy = 2

Take the reference from the screenshot: https://tinyurl.com/25fgmft2

After saving the above occupancy configurations of room type, the room can have a maximum of 2 guest occupancies.

So as per your requirement, you can assign the following combinations to the room in QloApps for a maximum 2 guest occupancies:
2 Adults, 0 Children
1 Adult, 1 Children

Thank You

@brian-belen

Till QloApps version 1.6.0, the supported version of Apache is 2.2 and In the WampServer 3.3.5, the provided version of Apache is 2.4.

We suggest you please use a WampServer version that has Apache version 2.2.

Hi @leokonwar

We do not found this error in the latest version of QloApps v1.6.0. So please mention which version of QloApps you are using currently.

Also, if there are any specific steps to reproduce this error, then please describe the steps also.

Hi @nazirul

This issue might be caused due to the use of a proxy server to host QloApps.

By default, QloApps is configured to check for the IP address of the cookies which in your case was failing whenever IP was getting changed. This default configuration has been disabled for now.

The configuration is located at:
Administration > Preferences > Disable "Check the cookie's IP address" option

Below is the attached screenshot for the same:
Preferences-•-Ashish-Lal.png

Thank you.

@nz-camper It seems to be due to the old domain still being saved on the database. We request you to update it to the required domain.

Please use the following guide to make the required changes to fix the domain issue on your server.

Migration guide: https://qloapps.com/how-to-migrate-qloapps-to-a-new-server/#section-3

Please make sure to make all the mentioned changes.

We recommend you go through the full guide for detailed information.

@nz-camper This setup should work fine. Just make sure the file changes are synced properly in all QloApps servers.

We are glad to inform everyone that we have released the QloApps Housekeeping Addon.

You can explore the demo of QloApps Housekeeping Addon and the user guide of QloApps Housekeeping Addon to learn about the functionality and configurations of the module.

Please follow this link to purchase the QloApps housekeeping addon from our store: https://store.webkul.com/qloapps-housekeeping.html

Hi @rav1971 ,

We acknowledge this issue and this is on our roadmap. We will provide you with a patch for the solution of this issue.

Hi @rav1971,

To authenticate using the Authorization header, you need to encode your API key in base64 as user:password pair. In QloApps, user is your API key and password is empty.

Please refer to https://devdocs.qloapps.com/webservice/basic-topics.html#authorization-header for using Authorization header in QloApps Api.

Hi @michi,

To translate this text in the controller you don't need to make any changes to the code. You can translate the error messages in QloApps with the following steps:

Go to "Translations" in the "Localization" tab.
Select the type of translation as "Error message translations" then select the language and click on modify.

selecte_translation.png

After this you will be able to update the translations for the error messages for the front controller.

update_translation.png

Hi @michi

The feature for Price per Person day is currently not available in QloApps but we have already added it to our roadmap for the next major release.

We will surely update you once our next major release is out.

Hi @travelwo,

If you have completed the email setup in QloApps and you remember the email ID that you have used, then you can click on forgot password to reset your password (http://tinyurl.com/yqla3ln9 ).

You will receive an email through which you can set a new password for your account.

In case you are unable to reset your password, then we request you to create a ticket and share your server details, website URL, and Database details on the ticket only. Our team will help you further accordingly on the ticket.

You can create a new ticket from here: https://webkul.uvdesk.com/en/customer/create-ticket/

Hi @rmorris,

QloApps by default supports MySQL version 5.1 to 5.7 for the database.

We suggest you connect with your service provider and tell them to install compatible MySQL on your server to install QloApps. This will definitely resolve your issue.

Hi, @kaziel ,

We have checked this at our end but found no issue in translations.
If there are any specific steps to reproduce the issue then please mention the steps. Otherwise, We have to check this issue on your server and for that, we request to kindly create a ticket and share your Admin URL, Admin credentials and FTP details with us.

You can create a ticket from here: https://webkul.uvdesk.com/en/customer/create-ticket/

@jamessou13

The SumUp checkout require payment scope which is restricted from SumUp end by default, Please check SumUp Documentation.
Please contact SumUp support to enable payment scope for your account.

If you are still unable to accept payment after enabling payment scope.
Please raise a ticket at https://webkul.uvdesk.com/en/customer/create-ticket/
And on the ticket please share your QloApps Credentials and FTP details so that we can look into the issue.