# Pinegrow WP Plugin is HERE ❤️🌲

**URL:** <https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401>\
**Category:** Announcements\
**Created:** [December 14, 2022, 2:58pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401 "2022-12-14T14:58:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 14, 2022, 2:58pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/1 "2022-12-14T14:58:23Z")

</div>

Hi, Matjaz from Pinegrow here.

(If you are not interested in building projects for WordPress, read on - Pinegrow WordPress Plugin is NOT just about WordPress)

It took us a while, but Pinegrow WordPress Plugin is finally here.

## What is Pinegrow plugin and how can you use it?

The plugin brings the power of Pinegrow editor directly to your WordPress site, letting you:

1. Create custom Gutenberg blocks for any WordPress site.
2. Build whole WordPress themes.
3. Have a self-hosted visual web editor for building HTML & CSS projects in the browser, similar to Pinegrow Online.

With (1) and (2) you are using Pinegrow to build projects for WordPress, and with (3) WordPress is just a backend for hosting the editor.

Plugins and themes created with Pinegrow do not require Pinegrow to run.

## Free and PRO editions

Pinegrow plugin is available in two editions: free and PRO.

The free edition is suitable for creating simple Gutenberg blocks for existing WordPress sites.

The PRO edition brings the full power of Pinegrow to your browser, including: building whole themes, blocks with sub-blocks, WooCommerce, GreenSock powered Interactions and the ability to import and export projects. Plus you get email support from our team.

## Pricing

The PRO edition is available with two yearly subscription plans:

- **Single site license** that lets you use Pinegrow on one site at a time (you need to deactivate the license on one site to use it on another). Regular price is USD 49 / year.
- **Unlimited sites license** lets you use Pinegrow on all your sites (including your client sites). Regular price is USD 199 / year.

If you cancel the subscription you will not be able to use Pinegrow plugin any more, but all your exported plugins and themes will continue to work.

[Get Pinegrow WP Plugin »](https://pinegrow.com/wordpress)

## 

How to get started with the Pinegrow plugin?

1. [Download the plugin](https://pinegrow.com/wordpress) and install it on your WordPress site. The best is to start using it on one of your development sites.

2. Activate the PRO edition by entering your license details or keep using the free edition.

3. Do the interactive **Build Your First Block tutorial** available from the Pinegrow dashboard inside WordPress dashboard to learn how to use the Pinegrow interface, create the HTML structure of the block, style it with CSS and then turn it into a fully editable React-based Gutenberg block with custom sub-blocks.

![Image](https://ci5.googleusercontent.com/proxy/9AO8eFCJvSG_cs9caWp01JeII83PKMQkM_f6EPmfh0XOm31REhi3LndBy1ik_Y9qio5LgTN-0E4w83uHqOqxdSeomYfl6IGBTMdTz8L8Tizu--nxXNyzSdcjdM5A2DoeE9YQhOaQNLnwAdlTcNo5vcib0ZFTEmTPcGs=s0-d-e1-ft#https://www.dripuploads.com/uploads/image_upload/image/2757942/ff4c2cb0-5009-4eab-9eff-efebc9c1e284.jpg)

In about an hour you will know enough to be able to create custom blocks for any WordPress site, assuming that you have some prior knowledge of HTML and CSS. This tutorial alone is worth the price of the license!

## How to safely use the Pinegrow plugin?

One important point to keep in mind is that Pinegrow plugin is used to manipulate PHP files directly on your site. Therefore, only trusted site administrators should be allowed to use Pinegrow. Please read our [guide on how to safely use the plugin](https://pinegrow.com/docs/wordpress/pinegrow-wordpress-plugin/how-to-safely-use-the-plugin/) to learn more.

## Huge Thank You! to all beta testers

They have been testing the plugin for the past three months, reporting bugs and giving feedback that helped us to launch the polished (hopefully) 1.0.0 release!

## Watch the launch chat to peek behind the scenes

Adam Lowe and I had a fun chat about the plugin launch, about the eight years of following Pinegrow’s approach to open web development and what else is in store for Pinegrow. [Watch the whole chat on YouTube.](https://youtu.be/3m7NlKq_wlM) We were aiming for 10 minutes but I just couldn’t stop talking 🙂

Hope that you will enjoy Pinegrow WP Plugin, as much as we enjoyed making it!

[Learn more & Get the plugin »](https://pinegrow.com/wordpress)

Have a great day,  
Matjaz and the Pinegrow Team

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 14, 2022, 2:59pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/2 "2022-12-14T14:59:14Z")

</div>



---

<div class="post-metadata">

**Author:** ![Pepper](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pepper](https://forum.pinegrow.com/u/Pepper)\
**Post date:** [December 14, 2022, 3:03pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/3 "2022-12-14T15:03:55Z")

</div>

What is the difference to Pinegrow Web Editor?  
I have Pinegrow Web Editor - 7.03 - PRO WordPress Personal + Interactions + Tailwind  
This is lifetime, the Editor works even if I dont’ purchase a further year and it is for unlimited websites.

Are the WP Plugin aind Pinegrow Webeditor 2 different products? Will there be any changes for Web Editor?

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 14, 2022, 3:17pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/4 "2022-12-14T15:17:24Z")

</div>

See the answer from the announcement:

> [@Emmanuel](#):
>
> The plugin brings the power of Pinegrow editor **directly to your WordPress site** , letting you:
> 
> 1. Create custom Gutenberg blocks for any WordPress site.
> 2. Build whole WordPress themes.
> 3. Have a self-hosted visual web editor for building HTML & CSS projects in the browser, similar to Pinegrow Online.
> 
> With (1) and (2) you are using Pinegrow to build projects for WordPress, and with (3) **WordPress is just a backend for hosting the editor.**

---

<div class="post-metadata">

**Author:** ![Pepper](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pepper](https://forum.pinegrow.com/u/Pepper)\
**Post date:** [December 14, 2022, 3:41pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/5 "2022-12-14T15:41:33Z")

</div>

May be I don’t understand “brings the editor directly to the WordPress site”.  
What is with my Pinegrow We Editor (Pro WordPress +Interactions + Tailwind)? Are there any changes or can I upgrade like I did in the past and the Web Editor keeps all features and is no subscription model?

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [December 14, 2022, 3:49pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/6 "2022-12-14T15:49:02Z")

</div>

@Pepper the PG WP Plugin is a separate product. There are no changes to Pinegrow Web Editor (the desktop app), both in terms of features and payment plans.

---

<div class="post-metadata">

**Author:** ![Pepper](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pepper](https://forum.pinegrow.com/u/Pepper)\
**Post date:** [December 14, 2022, 3:49pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/7 "2022-12-14T15:49:53Z")

</div>

Thank you very much 👍

---

<div class="post-metadata">

**Author:** ![Adryan](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Adryan](https://forum.pinegrow.com/u/Adryan)\
**Post date:** [December 14, 2022, 4:01pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/8 "2022-12-14T16:01:14Z")

</div>

Amazing, congrats. Bought already and wanted to try, but when I export the default project I’m getting an error ☹

Project export failed: Unknown error

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [December 14, 2022, 4:07pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/9 "2022-12-14T16:07:54Z")

</div>

@Adryan thanks! And you get the honor of reporting the first problem 🙂 The plugin logs results of API calls in the Console. Do you see anything if you expand the Object statement in the console after trying to export?

---

<div class="post-metadata">

**Author:** ![Adryan](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Adryan](https://forum.pinegrow.com/u/Adryan)\
**Post date:** [December 14, 2022, 4:21pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/10 "2022-12-14T16:21:02Z")

</div>

![obraz](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/d/d73a9da25f4547c6c4816ac79391c55465c62e0b.png)

It works fine on a fresh, local install.

I’ll try with a fresh, online install.

---

<div class="post-metadata">

**Author:** ![Wolfgang](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/wolfgang/32/2414_2.png) [@Wolfgang](https://forum.pinegrow.com/u/Wolfgang)\
**Post date:** [December 14, 2022, 4:29pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/11 "2022-12-14T16:29:10Z")

</div>

HI @matjaz  
started with the lessons building the first plugin. When I try to activate my first Plugin I get this error:

**Parse error** : syntax error, unexpected ‘\<’, expecting end of file in **/home/sites/server/server0/server1/public\_html/myserver/04/wp-content/plugins/pine-cone/inc/wp\_pg\_helpers.php** on line **302**

---

<div class="post-metadata">

**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\
**Post date:** [December 14, 2022, 4:46pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/12 "2022-12-14T16:46:29Z")

</div>

Well!  
Thank you for this!!

With the new tutorials, this plugin, the latest PG, and…crap, freezing weather, I may just have to clear some desk space and start tinkering again, in between chiselling my frozen boots off the floor at my horses.}  
THANKS!

\<3

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [December 14, 2022, 4:49pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/13 "2022-12-14T16:49:30Z")

</div>

Hi @Wolfgang, one reason could be that these resource files are not correctly loaded when the plugin starts. Please check Console for any problems loading files ending with phpdist.html, at the very start of loading the plugin and let me know.

---

<div class="post-metadata">

**Author:** ![ragandbone](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@ragandbone](https://forum.pinegrow.com/u/ragandbone)\
**Post date:** [December 14, 2022, 4:57pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/14 "2022-12-14T16:57:38Z")

</div>

I’m getting “the link you followed has expired. please try again” when I try to install.

What’s the best/easiest way to fix this?

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 14, 2022, 4:59pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/15 "2022-12-14T16:59:40Z")

</div>

Can you tell us more about the WordPress installation you are trying to install the plugin on (remote? local? etc…)? Any details are welcome.

---

<div class="post-metadata">

**Author:** ![ragandbone](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@ragandbone](https://forum.pinegrow.com/u/ragandbone)\
**Post date:** [December 14, 2022, 5:09pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/16 "2022-12-14T17:09:43Z")

</div>

I’m installing from my local disk to my active, hosted wp install.

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [December 14, 2022, 5:10pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/17 "2022-12-14T17:10:39Z")

</div>

Can you please provide us with some more details about your operating system, server app ? (mam,wamp,local.app) and so on ?

---

<div class="post-metadata">

**Author:** ![AllMediaLab](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/allmedialab/32/2079_2.png) [@AllMediaLab](https://forum.pinegrow.com/u/AllMediaLab)\
**Post date:** [December 14, 2022, 5:16pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/18 "2022-12-14T17:16:02Z")

</div>

Hi @Emmanuel and Pinegrow staff,

Congratulations with the new plugin!

Just wonder when reading the information about the use of the plugin:

> You can use your Pinegrow PRO license only on websites owned and operated by you, as well as client websites operated by you.

So when you make a website for a client that wants to maintain their WordPress site (them self’s) they have to buy a separate license.

To me It makes no sense then to purchase the Unlimited version, because that is only usable by users that build unlimited sites for them self’s. (wonder who that is!)

I mean If I have to build a site that has to be maintained with content by my agency for a client I would never chose for a dynamic website anyway.

So maybe an idea to look at that rule again, because that makes not much sense!

Regards,  
David

---

<div class="post-metadata">

**Author:** ![ragandbone](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@ragandbone](https://forum.pinegrow.com/u/ragandbone)\
**Post date:** [December 14, 2022, 5:26pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/19 "2022-12-14T17:26:49Z")

</div>

Mac OS 12.6, Not sure what else to say. I’m accessing my wp dashboard through Chrome (08.0.5359.124), so no separate server app.

WP install 6.1.1

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [December 14, 2022, 5:29pm UTC](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401/20 "2022-12-14T17:29:36Z")

</div>

Thanks @AllMediaLab!

“Operated” here refers to using PG plugin features of being responsible for the development of the site, and maintenance from that perspective - not content editing.

> [@AllMediaLab](#):
>
> So when you make a website for a client that wants to maintain their WordPress site (them self’s) they have to buy a separate license.

My logic goes like this:

a) If maintain means “editing the content” and you are still responsible for developing the site (even if there is no active work) then there is no need for them to get a license.

b) If maintain means that they use PG plugin to build new blocks, change the theme and so on - and you are no longer involved in the project - then it makes sense that they have their own license.

Does this make sense?

Note, that these limitations mostly have to do with closing loopholes that could be exploited by an non-honest actor: imagine a company selling some kind of product and bundling PG plugin in there, saying they own the license for unlimited sites.

[Next page](https://forum.pinegrow.com/t/pinegrow-wp-plugin-is-here/7401.md?page=2)
