Django Xiti
Django app to include Xiti loading code into your templates
This is a very basic app that does not contains any view, just a template tag to build the HTML code to load Xiti in your site pages.
It relies on Xiti parameters defined in your settings.
Links
Download his PyPi package;
Clone it on his repository;
Requires
Django >= 1.4;
Install
First install the package
pip install django-xiti
Add it to your installed Django apps in settings :
INSTALLED_APPS = (
...
'xiti',
...
)
Then fill your Xiti paramters in your settings:
XITI_CONF = {
'xiti_serverid': '', # Xiti server ID for usage on http protocole
'xiti_serverid_secure': '', # Xiti server ID for usage on https protocole
'xtsite': '', # Xiti site ID, also named 's'
'xtn2': '', # level 2 site ID, also named 's2'
'xtpage': '', # page name (with the use of :: to create chapters), also named 'p'
'xtdi': '', # implication degree, also named 'di'
'xt_an': '', # user ID, also named 'an'
'xt_ac': '', # category ID, also named 'ac'
'xt_multc': '', # all the xi indicators (like "&x1=...&x2=....&x3=...")
}
All these parameters are generated for your site from your Xiti account. xiti_serverid and xtsite values are required. If required values are not filled, xiti_code usage will raise a exception XitiSettingsError.
Loading ‘xtcore.js’
Finally, you must have the Xiti Javascript core file xtcore.js in your static. This file is not shipped into this app because it can be different from a site to another, you need to download it from your Xiti account.
When you got it, just put it as js/xtcore.js into your staticfiles directory. If you want to use another path or to load it differently you can override template xiti/include_js.html in your templates directory.
Generally, you should not try to load it without this template, because Xiti Javascript core must be loaded after parameters are defined else it won’t be able to use them, resulting in blank report.
Usage
Just use the template tag into your templates:
{% load xiti_tags %}
{% xiti_code %}
This tag does not accept any argument.
Metadata
Release files for django-xiti 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-xiti-0.1.1.tar.gz | 4.5 kB | Without provenance | Details for django-xiti-0.1.1.tar.gz |
Release files / django-xiti-0.1.1.tar.gz
| Download URL | django-xiti-0.1.1.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
347a7be8bbfa36ae0a01f8576d19a8003767c5f05d5a8c930a2e179b475c1b44
|
|
BLAKE2b-256 checksum How to use checksums |
b800e11281171e0205a6a8d42f144cf1100dd4790c19c8bb0977e8b50a6e75bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-xiti 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.