By searching the php code in the existing RightNow scripts, I have managed to put together a list of the various rn tags used and the attributes used. I have searched high and low for some documentation on these tags to no avail.
Can somebody point me to where I would find some documentation on this?
For the benefit of others this is what I have found in the scripts:
<rn:
----
condition
sla
logged_in
answers_viewed
searches_done
chat_available
config_check
url_parameter_check
show_on_pages
hide_on_pages
external_login_used
language_in
incident_reopen_deadline_hours
condition_else
widget (widget attributes will vary depending on the widget - those with a dash are included for standards adherence purposes)
path
-name
-label_input
-required
-table
-validate_on_blur
meta
title
template
login_required
redirect_if_logged_in
force_https
clickstream
sla_required_type
sla_failed_page
include_chat
javascript_module
answer_details
controller_path
compatibility_set
theme
path
css
field
name
label_input
highlight
page_title
head_content
page_content
block
id
form
post_handler
action
answer_xref
answer_section
container
report_id
---------------------------------------------------------------------------------------------------------------------------------------
#rn:
----
msg
session
language_code
php
url_param
url_param_value
config
php
community_token
---------------------------------------------------------------------------------------------------------------------------------------
Once you log into your Customer Portal admin site (whatever.custhelp.com/ci/admin), you can use the menu options to navigate to browse Page Tags / Page Meta tags under the Framework menu. Under Widgets, you will find all the widgets available for your site.
You can also read through the technical documentation located at cx.rightnow.com; here is a direct link to the answer page. Click on the Customer Portal portion and look under the Section titled "Customer Portal Template and Page Set".
Related
I don't want Pelican 3.6 to generate:
/author/
/category/
/tag/
/archives.html
/authors.html
/categories.html
/tags.html
DIRECT_TEMPLATES can be set to suppress some of the index files:-
# DIRECT_TEMPLATES = ['index', 'categories', 'authors', 'archives']
DIRECT_TEMPLATES = ['index']
Omitting tag metadata in source content files will prevent generation of the tag folder and index; omitting author metadata and the AUTHOR setting will prevent generation of the author folder and index.
But it seems that suppressing category isn't so simple. I've tried setting DEFAULT_CATEGORY to an empty string, but this results in errors and no output for sources with no category metadata:-
Skipping <some_file>: could not find information about 'NameError: category'
I've also tried removing the relevant template files from the theme being used, but this merely causes them to be replaced with the matching template in the built-in "simple" theme.
Am I missing an established method of suppressing category generation?
The URL settings documentation has a long list of settings, including several […]_SAVE_AS settings. Directly below the URL settings table is a note that answers your question: for any page type that you do not want generated, set the corresponding […]_SAVE_AS setting to ''. For example, to suppress individual category page generation, add this setting:
CATEGORY_SAVE_AS = ''
I am new to opencart and need help with oc 1.5.5.1
I am trying to call custom meta title to add last order id on checkout/success page. I have followed a very helpfull response from shadyyx on Opencart successful order ID and Total from JavaScript
Now I am stuck at a point on how to use the order_id which is already available in session and call / display it in meta title of checkout/success page.
As I understood you, you need to check if the orderid exists and not empty and route is checkout/success so for example add this to $this->data['my-new-metatag']
All above do in the common/header controller (cos meta tags are in the common/header tpl file)
then in common/header.tpl check if $my-new-metatag exists, echo it, otherwise leave variable that echos by default
I'm using the MediaWiki API to get the content of a Wikipedia page like this in JSON.
http://en.wikipedia.org/w/api.php?format=json&action=query&titles=New_York&prop=extracts
I'd like each section to be separated out instead of having the entire content of the page as one value. I know you can get each section like this but I want it to also include the content with each section.
http://en.wikipedia.org/w/api.php?format=json&action=parse&prop=sections&page=New_York
Is this possible to do with the API?
If you know the number of the section which you want you can get the contents through action=parse with the section parameter. E.g. the "19th century" section of the New_York article would be:
https://en.wikipedia.org/w/api.php?action=parse&page=New_York&format=json&prop=wikitext§ion=4
To get the section number you can use
http://en.wikipedia.org/w/api.php?format=json&action=parse&prop=sections&page=New_York
and then find the index corresponding to your section title (line). In this case "line":"19th century","index":"4".
I am working on a local listings website . I have to finalize the sitemap/link directory for the site to enable the search engine bots to crawl my site effectively (the end user is supposed to search using textboxes)
I have come with the following schema : Keywords(alphabetical order)=>City(Alphabetical Orders)=>Locality(in the city above , in alphabetical order)
Please note that at the three levels described above their are no actual profiles , just a bunch of more links , ex: keyword = xyz ; city = New York , Detroit , California , Minnesota
Locality = localities list of city chosen above .
This can be culminated in two ways :
1) At the third level I provide a link to search results page (the same a end user would see)
2) I simple list links of listed entities in the sitemap itself along with relevant info( which would be additional content for the bot to determine the links relevance)
Also is there a penalty for increasing the levels (3) here , should I consider going with two ?
Note : The search results page (as seen by end user) has pagination employed with links , not ajax .
To finalize with your sitemap, you can put a link on your keywords, cities and localities also. It will help for the users to navigate your website very easily.
If you go with more increasing level with third stage then it will look like too many links on a single page. So, Google will ignore your page and it will not indexed. So, you will loose the chanse of SEO benefits.
So one of my clients has a request to do rule based static blocks on their home page. The page will basically swap out several static blocks for others based on the perceived gender of the person viewing the site. It will get this data from the session that the user is currently in, or the data associated with the users account. Basically, if a user searches in a specific set of categories (Men's or Women's categories) it should swap the static blocks out on the home page, so when that user visits the site again they will have a more personalized experience. There will be a default set of blocks if the user is new to the site.
Something like this (and excuse my shabby php):
if($categories = $user->getViewedCategories()){
foreach($categories as $category){
switch($category){
case 14: //insert womens category id here
echo $staticBlockWomen
break;
case 16: //insert mens category id here
echo $staticBlockMen
break;
}
}
} else {
echo $staticBlockDefault
}
I know Magento tracks a users path through a site, and I know that other elements in Magento can have rules based on this data (the dynamic banners and checkout rules), but I am really lost on where to get started.
If someone could point me in the right direction, any help would be appreciated!
Cheers,
Matthew
I'm assuming you know the basics of Magento (at least how to create new blocks and how to manage the layout using xml).
If you need more info about that,
You can accomplish what you need in a few steps:
1 - create the blocks you need (create a new module and block classes inside it within the corresponding .phtml files)
2 - from the admin panel, select the category for which you want to add a block and navigate to "Custom Design" tab, then add in the "Custom Layout Update" textarea something like this:
<reference name="content" >
<block type="mymodule/myblock" name="myblock" />
</reference>
This way, every time the selected category is viewed by the custmer, a block of type "mymodule/myblock" will be added in the content area.