Hi Friends, I am currently working for customizing support suite version 4 according to my company requirements. I just started and my problem is that when I am trying to logging in at admin part, then after entering username and password, it is just displaying '1' at the page. I am trying to find out but not getting from where this is coming. Can anyone please have any idea. Also I need to customize the support suite v4 now.
I did this for kayako version 3., but it seems a lot different this time. Can anyone get me any idea please that how can I get that, which file is being used by looking at the URL. In the last version, we were able to look at index.php?query string but cannot see any thing this time. Please advise. Many thanks in advance Abhishek.
Hi Thanks for reply. We recently purchased a new fusion 4 for our new website and trying to install that so I didn't upgrade. Our old websites are still running Kayako version 3. We are at Linux server / PHP version 5.2.16 / ISO -8859-1.
@Jamie: How can I enable Login share please. I am not sure for this.
At page, when I am entering details it is taking me at./support/admin/index.php?/Core/Default/Login. It is just displaying '1'. View source is also only '1'. Please suggest. Thanks Abhishek. As Jamie suggests, the support guys will be able to help you out, but a good starting point is the difference in URLS.
It sounds like there is a mismatch between where you have put the files on your server, and the URL you entered when installing version 4. If you uploaded your files to wwwroot/support/ then when you installed your helpdesk, you should have ran it from and when prompted, the url for your helpdesk should have been It is important they match, as the setup script cannot actually change the locations of the physical files, even if you alter the URL Gary.
Thank you for contacting Kayako. I have created recurring tickets. Where and how do I make changes to the recurrance after they have been initially setup?
Invizimals video game. I want to change the dates of the recurrance. We would like to inform you that it is not possible to edit the recurrence after it has been initially setup in the help desk. However, we have added the same as an improvement at our bugs and improvements portal. You may refer to the following link to check the updates: Our developers will try to implement this feature in future builds. Also, how can I delete the recurrance? The required functionality is not implemented in v4, as of now. However, to remove the recurrence from the help desk, you may clear the 'swticketrecurrences' table from the database, with the following MySQL query: delete from swticketrecurrences; Also, we have already added the mentioned feature as 'Improvement'.
For more information, you may refer to the above mentioned link. In addition, the wiki states that you can set a ticket's recurrance Date and Time. I don't see an area to change the Time, I see Date only? Please note that there is no such option to set the time while setting up the ticket recurrence.
The next recurrent ticket will be created at the same time, when the original ticket has been created in the help desk. Please let us know if there is anything else we may assist you with. The best way to remove them is to just login to phpmyadmin or whatever mysql interface you have, search for swticketrecurrences and delete entries you want to remove really you could login via ssh, if you arent experianced with using SSH or MySQL via shell be careful! Or make a backup (mysqldump -u root -ppassword database databasedate.sql) # mysql show databases; find the kayakodatabase(whatever name you have setup) use kayakodatabase ^^ select.
from swticketrecurrences; this way you can see all the tickets /id numbers for deletion DELETE FROM swticketrecurrences WHERE ticketrecurrenceid = the id of the ticket you want to stop essentially looking at the table structure you can update the ticket this way, which doesn't look too hard to do(but its prob easier to just remove it and recreate if needed).
RELEASE INFORMATION As of January 2015, Webmail is discontinued. The latest version of FileCatalyst Webmail (v4.9.6 release date: Feb 24, 2016) only contains critical fixes and updates. The Windows Installer for Webmail has been discontinued starting in version 4.9.6. Until Aug 30th, 2016 only critical updates to Webmail will be released. No updates to Webmail will be offered after Aug. All the functionality of Webmail is now included in a product called FileCatalyst Workflow.
Posted by - NA - on 10 February 2007 01:47 AM How to configure Paypal Payflow Link? (note-The module is still labeled Verisign Payflow Link in your Miva Merchant administration interface) Payflow Link is the lower-tier payment gateway service that Paypal is currently offering to consumers.
First, to enable the Paypal Payflow Link module in Miva Merchant, follow these steps: 1. Log into the Miva Merchant Administrative Interface. 2. Expand the 'Stores' menu. 3. Expand the Store being worked on.
4. Click Payment Configuration. 5. Check the box next to: 'Verisign Payflow Link.' 6. Click the Update button. Once updated, a link for 'Verisign Payflow Link' will be displayed at the top of the screen. Click this link to configure the actual settings for the account: 1. Click the link at the top of the screen labeled 'Verisign Payflow Link' 2. In the field labeled 'Partner:' specify the Partner ID you get from your payment processor.
3. In the field labeled 'User ID:' specify the Paypal login id (not the Miva Merchant Login ID). 4. In the field labeled 'Password:' specify the Paypal password (not the Miva Merchant password). 5. The default URL in the field labeled 'URL:' is incorrect. It should be changed to the following: The values should be changed to match the correct information.
The LoginID is the same as the one entered in the first field. The Partner ID should be provided to the merchant when they sign up for the Payflow Link Account with Paypal. 6. Once all of this information has been entered correctly, click the 'Update' button. See Below: The rest of the fields can be configured to the customer's needs. It is up to them, and their arrangement with Verisign to determine what these settings should be. Type of Transaction: - Authorize Capture - When selected, this setting will authorize the credit card and capture the funds immediately when a shopper submits the information. This means that the shopper's card will be charged right away.
Authorize Only (Capture Later) - When selected, this setting will only authorize the shoppers credit card for the funds. It will be up to the merchant to log into the Verisign Manager to capture the funds. Available Payment Methods: - These selections indicate the type of payment methods that merchants will be allowed to use. These must be setup with Paypal beforehand. Generally, additional methods like 'Telecheck' will cost an additional monthly fee.
Those are the necessary steps for configuring the Paypal Payflow Link module inside the Miva Merchant interface. There are a few more steps that need to be completed in the Paypal Manager to finish the process. The Paypal Manager can be accessed at the following URL: Please follow the steps on the following pages to complete the configuration for the Verisign Payflow Link payment gateway. Access the Verisign Manager at: 1. Login at the Paypal Manager login screen. 2. Click on Service Settings On the page displayed are different settings that the merchant can configure to his/her needs.
This document will detail only those that are pertinent to Miva Merchant. Specifically the settings found in the section headed: Form Configuration. 1. The menu labeled 'Return URL Method' should always have 'POST' selected. This is the only way that Miva Merchant will interact with Payflow Link. 2. The field labeled 'Return URL' is also very specific. It will contain the URL to the file on the Merchant's site that will accept feedback from Payflow Link and build the final invoice.
It should be: Merchant v4.x: Merchant v5.X:. Verify secure URLs from within Miva Merchant Administration Site Configuration. Please be sure to change the URL to reflect your correct secure URL information. 3. The field labeled 'Silent Post URL' is also very specific. The box should ALWAYS be checked.
It will contain the URL to the file on the Merchant's site that will accept the order information from Payflow Link and store it inside the Miva Merchant Admin. It should be: Merchant v4.X: Merchant v5.X:. Verify secure URLs from within Miva Merchant Administration Site Configuration.
Please be sure to change the URL to reflect your correct secure URL information. 4. The box next to 'Force Silent Post Confirmation' should also be checked. This forces Payflow Link to verify that it can communicate with Miva Merchant before actually processing the order. It is very important that they can 'talk' to each other. The field labeled 'Failed Silent Post Return URL:' will provide the location where the shopper will be directed in the case that communication between the applications fails.
Kayako Help Desk Log In
It can be to any location on the website, but it is a good idea to point the user back to the storefront, or to an HTML page explaining the problem and requesting that they contact the merchant directly. 5. Transaction Process Mode should be set to whatever the customer needs at the time.
If 'TEST' is selected, none of the credit cards submitted through the account will be charged, and test credit card numbers will be accepted. When 'LIVE' is selected, all credit card numbers will be authorized and funds will be capture-able. 6. Scroll to the bottom of the page and click the 'Save Changes' button. All other settings on this page can be changed to suit the merchant's needs. It is important that they refer to Paypal-Provided documentation before making any changes to this area.Note: Force Silent Post Confirmation may not be supported by your webserver. For this feature to work, the webserver needs to allow a '200 message' to be sent through so PayFlow Link knows that Miva Merchant has received the data. If your transactions are automatically being voided, one thing yo u can try is disabling the Force Silent Post Confirmation.
If that does not resolve the issue, contact Verisign support. Changes must also be made to the configuration of Miva Merchant's Verisign Payflow Link Module. This is used to send the information to Verisign.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |