rockiger

Hello @afshinmoshrefi,

first make sure, that you follow steps in the usage information (https://www.ads-software.com/support/plugin/reactpress/), step by step. Exactly in that order.

The slug needs to be available, and it can’t be a child page. It needs to be DOMAIN/YOUR-SLUG. If another page already uses this slug, even a page in the trash, ReacPress won’t work.

If this doesn’t work for you, I would recommend, that you try it with Local as dev environment.

@humbi1992 I looked into the problem. Unfortunately I don’t have any idea what the problem could be.

As far is I understand Elementor hacks deeply into the template system to do its magic. Probably the problems will originate there.

Maybe you could ask at their support forums to give you a hint, what the problem could be.

No, sorry. It slipped through my list.

I will look into it this week.

Hello @starnizar,

this seems like a configuration error with your WordPress installation. Try a different local dev server like https://localwp.com or https://kinsta.com/devkinsta/.

Tell me if you still have problems.

• This reply was modified 3 years, 9 months ago by rockiger.

Did you try uploading your react according to the documentation?

Try uploading your app with ftp, without any wordpress plugins. You need to create a new React app on your live system. Use the exact same name and this time choose “Deploy an already build app (Usually on a server).” – This is key.

It seems that you need to talk to Aruba to activate these exec and shell_exec.

And try to upload your React app by hand, according to the documentation.
Maybe this fixes things

Is this a local development server or a server provided by a hoster?

For the local development server check the configuration.

For the later contact your hosting provider.

Hello lidia,

if your server doesn’t have access to shell_exec and exec, ReactPress can’t execute the commands, it needs to create React apps.

Thank for reporting this. I never used elementor. I will look into the error.

The error doesn’t make any sense to, because the plugin doesn’t do anything with the pages except creating one where to display the React app.

@ianuminc

I released a new version. It has a fallback for the apps directory. So it shouldn’t make any trouble.

This release does change the way to use ReactPress and gives you much more control.

Nonetheless, backward compatibility should be given.

I released a new version

It should solve a lot of issues with using ReactPress in local development environments like Local, DevKinsta, and similar.

This release does change to way to use ReactPress and gives you much more control.

Nonetheless, backward compatibility should be given.

I released a new version

It should solve a lot of issues with using ReactPress in local development environments like Local, DevKinsta, and similar.

This release does change the way to use ReactPress and gives you much more control.

Nonetheless, backward compatibility should be given.

Hey Paul, I created a new release that should work better for you.

This release does change the way to use ReactPress and gives you much more control.

It should solve a lot of issues with using ReactPress in local development environments like Local, DevKinsta, and similar.

Nonetheless, backward compatibility should be given.

• This reply was modified 3 years, 10 months ago by rockiger.

The new release is out. This release does change to way to use ReactPress and gives you much more control.

It should solve a lot of issues with using ReactPress in local development environments like Local, DevKinsta, and similar.

Nonetheless, backward compatibility should be given.

Can you try and give the VM more RAM – maybe 2 GB.

I am planning to publish a new version of ReactPress over the weekend, that will allow you to use create-react-app right in the apps directory.

I hope, that users won’t need the VM anymore.