Tin Canny for WordPress provides an easy-to-use interface for managing uploaded content.
Access the page at Tin Canny Reporting > Manage Content to:
Upload new content
Search uploaded content by title
Sort uploaded content by upload date
Preview uploaded content (note that xAPI statements will be tracked when you preview content)
Replace content
Delete uploaded content
Manage xAPISCORM content in WordPress
Replacing Content
Previously, to replace content meant:
Uploading the updated content as a new module
Replacing all existing shortcodes/blocks to point to the new module
Deleting the previous content
This process also meant that any completion records tied to the previous module would be lost, since the module’s ID would have changed.
However, on the Manage Content page, replacing an existing module is easy. Simply click Replace from the Actions menu:
This launches a dialog that asks what you want to do with data recorded for the existing module. There are two options:
Delete bookmark (resume) data only: This option deletes stored the bookmark data that prompts users to resume from where they left off in the module the next time they visit it. This data must be deleted whenever content is replaced as internal bookmark IDs may have changed, resulting in the existing bookmark data preventing the module from loading properly.
Delete all data: This option deletes both stored bookmark data and stored xAPI statements (the data shown in the Tin Can and xAPI Quiz reports).
Note that the data is deleted immediately after selecting one of the above two options, even if the actual replacement is cancelled in the following steps. (This workflow provides a roundabout way to delete all data for a module even if you don’t want to replace it; simply select one of the above options, then cancel the replacement in the following step).
Once the replacement module has been uploaded, the updated content will appear wherever the previous module had been embedded.
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Easy Digital Downloads is a WordPress plugin for selling digital products effortlessly and managing transactions.
Name
Description
Duration
edd_session_
Stores information about the current user session.
Session
edd_items_in_cart
Stores information about the cart contents.
Session
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
Stripe is a payment processing platform that enables businesses to accept online payments securely and efficiently.