=== Embed Google Drive ===
Contributors: rtCamp, sh4lin
Donate link: https://rtcamp.com/
Tags: Google Drive, embed, spreadsheet, document, drawing
Requires at least: 5.5
Tested up to: 6.8
Requires PHP: 7.4
Stable tag: 1.2.2
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Embed a link and preview of Google Drive Documents by pasting a shared document link into the editor.
== Description ==
Embed a link and preview of Google Drive Documents by pasting a shared document link into the editor.
No configuration is required.
### BTW, We're Hiring!
[
](https://rtcamp.com/careers/)
== Installation ==
1. Download the plugin from [here](https://wordpress.org/plugins/embed-google-drive/)
2. Add the plugin from the WordPress admin panel.
3. Activate the plugin through the 'Plugins' menu in WordPress
== How to use ==
1. Copy the URL of drive document which you want to embed. Note: The document must be shared with anyone with the link.
2. Create new post/page or edit existing one.
3. Paste the URL in the editor. It will automatically embed the document.



== Frequently Asked Questions ==
= Reporting a bug 🐞 =
Before creating a new issue, do browse through the [existing issues](https://github.com/rtCamp/embed-google-drive/issues) for resolution or upcoming fixes.
If you still need to [log an issue](https://github.com/rtCamp/embed-google-drive/issues/new), making sure to include as much detail as you can, including clear steps to reproduce the issue, if possible.
= Creating a pull request =
Want to contribute a new feature? Start a conversation by [logging an issue](https://github.com/rtCamp/embed-google-drive/issues).
Once you're ready to send a pull request, please run through the following checklist:
1. Browse through the [existing issues](https://github.com/rtCamp/embed-google-drive/issues) for anything related to what you want to work on. If you don't find any related issues, open a new one.
2. Fork this repository.
3. Create a branch from `develop` for each issue you'd like to address and commit your changes.
4. Push the code changes from your local clone to your fork.
5. Open a pull request and that's it! We'll respond with feedback as soon as possible (Isn't collaboration a great thing? 😌)
6. Once your pull request has passed final code review and tests, it will be merged into `develop` and be in the pipeline for the next release. Props to you! 🎉
== Changelog ==
= 1.2.2 =
* Renamed the main plugin file and primary class for alignment with naming conventions.
* Updated the plugin’s constants, package headers, text domain, and REST API namespace.
* Regenerated the .po translation file to include updated metadata and renamed references.
= 1.2.1 =
* Chore: Plugin tested up to WordPress 6.8
* Chore: Doc update
= 1.2 =
* Chore: Plugin tested up to WordPress 6.7.1
* Chore: Doc update
= 1.1 =
* Plugin tested up to WordPress 6.4.2
* PHP Version updated to 8.0
* Fixed PHP Coding Standards issues
* Plugin is VIP compatible
= 1.0.1 =
* Jetpack compatibility.
= 1.0 =
* Initial release.
== Upgrade Notice ==
= 1.2.2 =
* Renamed the main plugin file and primary class for alignment with naming conventions.
* Updated the plugin’s constants, package headers, text domain, and REST API namespace.
* Regenerated the .po translation file to include updated metadata and renamed references.
= 1.2.1 =
* Chore: Plugin tested up to WordPress 6.8
* Chore: Doc update