Elxis CMS Forum

Extensions => Components => Topic started by: rulez22 on November 15, 2010, 14:56:22

Title: understanding the usage of IOSR 3.5 component
Post by: rulez22 on November 15, 2010, 14:56:22
Since I upgraded 3.3 to 3.5 i have some problems - some menus are repeated twice:
like when user login he can see "Control panel" (Manage your hotels and your reservations) twice
Also currency select box is repeated twice
Is it because it is not separate anymore and currency and control panel is included in the main component?
I dont see how I can separate this and put in different places on the page
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 15, 2010, 23:30:11
It is absolutely impossible to do "stop sales" in current system.
Since upgrade "not available" thing disappeared, so you cannot put stop on room sales, people booking rooms which are not available! "Use vacancy" option has no use here!
It is also still impossible to do it manually, because not only dates are showing in wrong format (YYYY-MM-DD) but you also have to think about how to "squeeze" stop sales in these seasons.

Would still be nice to see credit card charge in percentage of total balance - it is not hard to make is it?

In "updates"
Destinations (Displays IOS Reservations v3.5+ destinations. Many options to set your desired display style. Requires Elxis 2009.2+ and IOS Reservations 3.5+) - is showing not installed (in red), when it is installed
Also same with "Offline Credit card
Payment method that allows you to process credit cards offline. v1.1 fixes an authentication problem in the decrypt feature. For IOS Reservations 3.0, 3.1, 3.2 and 3.3"
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: datahell on November 16, 2010, 12:33:05
I dont see any bug report in your post. Where are the bugs?

For the things you see twice:
This is because you display them both in your layout and you have also published the corresponding module. Display one of them, not both.

"stop sales" is match easier than before. In v3.3 you had to set stop sales day by day. Now you can set a whole season as "stop sales" by setting room's vacancy to zero. In v3.3 stop sales was controlled by the "special availability" which removed in v3.5. This is 1 of the 2 things that can not be transfered to v3.5 and the updater clearly says that you will lose special availability during update and you will have to re-enter these days by using the "seasons price".

Why the date format "YYYY-mm-dd" is wrong? This is the main part of the global standard date format (YYYY-mm-dd HH:ii:ss)
Which is the problem with the "Destinations" module? It says that it is compatible to v3.5+ only.
"Offlijne credit card" is included in v3.5, you dont have to download the payment gateway.
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 16, 2010, 14:15:25
For the things you see twice:
This is because you display them both in your layout and you have also published the corresponding module. Display one of them, not both.

"stop sales" is match easier than before. In v3.3 you had to set stop sales day by day. Now you can set a whole season as "stop sales" by setting room's vacancy to zero. In v3.3 stop sales was controlled by the "special availability" which removed in v3.5. This is 1 of the 2 things that can not be transfered to v3.5 and the updater clearly says that you will lose special availability during update and you will have to re-enter these days by using the "seasons price".

Why the date format "YYYY-mm-dd" is wrong? This is the main part of the global standard date format (YYYY-mm-dd HH:ii:ss)
Which is the problem with the "Destinations" module? It says that it is compatible to v3.5+ only.
"Offlijne credit card" is included in v3.5, you dont have to download the payment gateway.

I did set room to 0, there is also option "use vacancy", if set to no, then room will be sold even if it has 0 available, isn't it?

By the way how do i add some little html text in top right corner (user1 position)? Like telephone number for the company - what do i need to edit?

date format "YYYY-mm-dd" is not human format, but database format, as you can understand office managers who insert prices are not familiar with php/mysql, they just want to add prices and stop sales, it would be best to have it dd/mm/yyyy or dd-mm-yyyy

In regards of Destinations module and Offline credit card module - i said it was a bug, because it is installed, but in red it says NO, not installed. It is clearly not correct

Thanks for your response!
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: datahell on November 16, 2010, 14:23:54
If you dont use vacancy then rooms are always available.

Go to modules, click new, add the text you like in the editor's text area and assign your new user module on position "user1".
You can set the date format in frontend, in backend it is always YYYY-MM-DD
The info if it is installed or not is not always available and depends on the type of extension. It is complicated to explain you why from here and it is not important.

From what you have written there is no bug report.
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 16, 2010, 14:35:42
If you dont use vacancy then rooms are always available.

Go to modules, click new, add the text you like in the editor's text area and assign your new user module on position "user1".
You can set the date format in frontend, in backend it is always YYYY-MM-DD
The info if it is installed or not is not always available and depends on the type of extension. It is complicated to explain you why from here and it is not important.

From what you have written there is no bug report.
well, thats the thing, we dont use vacancy at all (it is always set to 10) and there is no way I can have stop sales (rooms are always available when they are not)

regarding "user1" i did that - it puts a rounded corner css frame around the code i put in, is there a way to disable it?

yes dates are just like you said, it's just complicated to put them in that way in backend.

many thanks
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: datahell on November 16, 2010, 19:13:15
It is easy to change that.
IOSR 3.5, file administrator/components/com_reservations/includes/availability.class.php

Find line 306:
if ($resmaster->cfg->get('VACANCY') && ($this->quantity > $this->vacancy)) {

Add before:
if ($this->vacancy < 1) {
   $this->errormsg = $resmaster->lng->SORNOAVROPER;
   return false;
}

Set the module css suffix to change the module's appearance (depends on your template).
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 20, 2010, 03:55:09
When I add/change description on hotels it doesnt save anything! Just blank, when I press WYSYWIG button "HTML" it also shows empty source code.
Strangely it also shows 2 windows.
How do I fix this bug?



[attachment deleted by admin]
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: datahell on November 20, 2010, 08:35:28
There is no problem on the editor... Hit control+f5 to refresh your browser's cache. Might the new IOSR javascript has not be loaded.
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 23, 2010, 06:49:58
In Elxis configuration i've turned WYSIWIG from NO - in to TinyMCE and it works fine now
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 23, 2010, 08:39:13
I've created a test reservation, it didnt ask me for username, but for firtsname, last name, telephone, email, etc. Then I've logged in to backend and can see the reservation with username "-"
Cannot login as that user, password reminder also says "no corresponding user found", is it a bug?
Title: Be more careful
Post by: datahell on November 23, 2010, 13:31:04
Stop posting bug reports while there are no bugs!

Please pay attention to IOS Reservations configuration. You have enabled the option to allow bookings without user registration. So, the system, works as you have set it to work. If you want people to login in order to book a room then set "user registration" as required in IOSR configuration.
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: rulez22 on November 23, 2010, 14:14:57
Apologies,
yes, the option to allow reservations without login is on
but that means that they cannot login because they have no login details, only way to track reservations for them is via /track.html?
Title: Re: Bugs since upgrade 3.3 to 3.5
Post by: datahell on November 23, 2010, 14:45:43
If they want to register they can register. Track page works for both registered and un-registered users. So, anyone can track the status of his reservations. Registered users can see a list of their reservations from the "my reservations" page (SEO PRO URL: /myreservations.html )
Title: Friendly Suggestion
Post by: webgift on November 23, 2010, 16:24:31
rulez22 ,
There is a different approach to the definition of words like: "Bug" and "understanding the usage of IOSR 3.5 component".
For any misunderstanding of forum's visitors please rename the name of this topic.

Friendly suggestion!