Expected duration: 1-3 months if possible INTRODUCTION We need help customizing a Joomla extension we are using on two websites. The extension is a restaurant table reservation system for Joomla. (FYI, this job is not about just changing some Joomla backend settings or changing some CSS for a Joomla template, you will need PHP coding knowledge etc.)
WEBSITE INFORMATION Both websites are for a restaurant. Both websites are 100% live, but I can install clone versions of the sites on a different server, where you can test and work on. You will get access needed to work (FTP/MySQL/JoomlaSuperAdmin). CMS: Joomla 3.9 Extension: VikRestaurants (component, module, plugin) The extension has very good API docs and the extension itself has API functions built in to make things easier, and you can use our “paid for support account” to ask questions to the devs. Here are the docs: https://extensionsforjoomla.com/documentation/vik-restaurants-apis and https://extensionsforjoomla.com/documentation/vik-restaurants-plugin-events
CUSTOMIZATION DESCRIPTION The websites are for restaurants and the extension “VikRestaurants” is a table reservation solution for Joomla. There is no payment or e-shop or takeaway functions on the site, it is pure info websites, and the table reservation system. I (Thomas) made the websites and everything works fine. But there are some features that the client requests that the extension does not do, that I cannot customize it to do. So, to be clear, everything works fine, its matter of some tweaks of the extension to make it work more like the client want it to work. Most of the changes we need are in the back-end admin of the extension, but some in front-end admin and some are for the public site view.
Here are the changes we need: (If these descriptions of the customizations we need are difficult to understand, I can create screen videos and print screen images to better illustrate what we need, and you can get access to the website and extension to take a look)
1) - Reservation Module We use the module “VikRestaurants Quick Reservation“ where visitors can make a reservation. > How it works now: In step 1, they choose date/ time/ amount of people. In step 2, they choose room. In step 3, they fill in first name/ last name/ e-mail/ phone number. > How we want it to work: Step 1, they choose room/ date/ amount of people. Step 2, they choose time (times shown that they can choose from, must be available times according to their previous choices) Step 3, they fill in first name/ last name/ e-mail/ phone number (no changes for this step)
2) - Average Time of Stay > How it works now: In the back-end settings for the component, you choose “Average Time of Stay”, and then all new reservations made, automatically have that reservation time. We can manually change time of stay for a reservation in back-end and front-end admin. > How we want it to work: We need to be able to set different “Average Time of Stay” for each room (we have 3 rooms). It is ok if it is done only in file codes, we do not need a new field in the component settings, as long as you can say what files and line, we can change the stay times.
3) - Maximum People > How it works now: In the back-end settings for the component, we choose minimum and maximum people, that visitors can choose to make a reservation for. > How we want it to work: We need to have different amount of maximum people for each room.
4) - Group Reservations > How it works now: The reservation system has a “table cluster” function, which means that in back-end, we can choose to have several tables in a “cluster”. For example if you have 2 tables (each with max capacity 4 people) in a cluster, when someone makes a reservation on the website for ex. 8 people, the system makes a reservation with both tables, like a “group reservation”. Now we can only create a group reservation (table cluster) on the public front-end, not in back-end. > How we want it to work: We need to be able to create group reservations back-end, to be able to choose any number of people and choose several tables for a reservation.
5) - Reservation Notes > How it works now: You can see reservation notes in front-end operations table view when clicking on a reservation. > How we want it to work: We need to be able to see reservation notes in front-end operation list view also, when clicking a reservation.
6) - Print Button > How it works now: In back-end reservation list view, there is a print reservations button. > How we want it to work: We also need to have a print reservations button in front-end operation list view. And change the layout a little bit for the “print friendly” view the button produces.
Important! All customization must survive future Joomla and extension updates, so they should be made with overrides, or if you provide codes and instructions of what files should be changed, or if you can implement the customization again in the future if it stops working.
