# ig2wp Export Instagram Posts into WordPress Posts
# Requirements
Have WordPress Administrator Prvileges
Have Username/Password to Instagram Account
# Instructions
## Create a WordPress Application Password
Navigate to your blog’s /wp-admin endpoint and on the left sidebar, select Users.
Select a user with media and posting privilieges. Your administrator user is fine.
Scroll to the bottom where it says “Application Passwords”. Add a new application password. Give it whatever name you want. Hold onto these credentials.
## Install and run the Instaloader application
Visit the [Instaloader Github](https://github.com/instaloader/instaloader) for information on installation, configuration, and exececution.
Upon running the application, you will have a directory containing files ending in .json.xz, .jpg, .mp4, and .txt. Make a note of this directory location. You will need it later.
## Install the IG2WP Application
Install the IG2WP python application from source. You may pip install directly from Github as shown below.
` pip install git+https://github.com/aderbique/ig2wp.git `
## Configure and Run the IG2WP Application
You have the option of specifying the parameters on each runtime, or by saving the contents to a configuration file. The -w parameter writes your variables to the config file for you.
` $ ig2wp -s https://my-wordpress-blog.com -u <your wp username> -p '<the application password you generated>' -d </path/to/instaloader/account> -want `
Example:
` $ ig2wp -s https://blog.derbique.us -u austin -p '5EC5 PpLf 5rVn Ekwe 8JWE KWEP' -d '~/instaloader/austinadventure' -w `
### Modifying the Configuration file
Simply edit the file after it’s generated
` vim ~/.ig2wp/config.ini `
# Bug Reporting
Please submit bug reports through Github
Metadata
Release files for ig2wp 0.1.0
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 |
|---|---|---|---|---|
| ig2wp-0.1.0.tar.gz | 7.3 kB | Without provenance | Details for ig2wp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ig2wp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ig2wp-0.1.0-py3-none-any.whl |
Total release size: 15.5 kB
Release files / ig2wp-0.1.0.tar.gz
| Download URL | ig2wp-0.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f75dde0a4e6d5c9d2addb5aca802d1d8096e699a25e500b2eaec8eb2d7f8501b
|
|
BLAKE2b-256 checksum How to use checksums |
dcc12a1036410f84ee74914cbb9d48d69af1ce8a35b2ff31b6b00e5806d56e9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.46.0 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.3 CPython/3.8.10
|
Release files / ig2wp-0.1.0-py3-none-any.whl
| Download URL | ig2wp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
97e19d5763ab4379e089f4360b83bca83049942f6cdd15cc79035267536ff2d4
|
|
BLAKE2b-256 checksum How to use checksums |
b7844e327b98573cdf2d2a7062d9890898d6aed5ae37233658acfc241da76d43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.46.0 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.3 CPython/3.8.10
|
Security for ig2wp 0.1.0
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.