Pro Beta 6.0 rc1 - WP Cost Estimation & Payment Forms Builder Conflict

Beta
#1

Hi,

There appears to be a conflict caused by the bundled extension WP Cost Estimation & Payment Forms Builder. With the extension activated, if I go to Page > Page Name I get a blank screen with no ability to edit the page in anyway. Using the page’s Edit With Cornerstone link, I can edit the page’s content normally. It is just the default WordPress page settings which cannot be accessed.

If the extension is deactivated I get all the expected page editing features.

Are you able to replicate this one?

Thanks,
Christopher

#2

I’m not seeing this issue when that extension is activated. You are referring to the gutenberg / WordPress page editor correct? Are you getting any errors or warnings? Do you have a site I could access and see?

#3

Hi Charlie,

Details in a secure note.

Thanks,
Christopher

#4

Thanks I’ll take a look.

#5

Did you manage to get anywhere with this issue? It still persists when the plugin is enabled. To reiterate, in the WP admin, if I click on Pages in the left menu and then click on any page to open it, I receive a blank screen. For a page that has been built with Cornerstone, I can successfully get into Cornerstone to edit the page, but if I click the page’s main link to get into its basic settings / Gutenberg, I get the blank screen.

#6

Looking into right now

#7

You are getting a rest authorization error. In this case it’s based on post type. I’m bringing it up in case you are creating custom post types. The property that should be true is show_in_rest.
If not, In your DB what is the post type of id 350?

image

#8

Hi @charlie, the post type for id 350 is “page”. There should be no custom post types anywhere on this website. That page is set to “private” and it contains a couple of WP Cost Estimation forms. The page can be safely deleted, if required.

1 Like
#9

Did this work in the last version of pro? Were you ever using the premium version of wpforms and switched to the lite version? I see where I can add a workaround by adding show_in_rest and then after that there is a permission issue as if this rest route isn’t setup, but it seems like what’s happening on your end is a wpforms issue. I’ll bring your site into my environment and see if I can get more answers there.

#10

This website was built in Pro Beta 6.0 (v.3 to RC1) alone, not in v5. It is also the only website I have attempted to use WP Cost Estimation on!

WPForms is also only the bundled Lite version included with Pro and the premium version has never been used.

I hope you find the root of the problem!!

1 Like
#11

This one still alludes me. WPForms loads completely differently on my site then yours even after bringing your content into my site. It’s 100% something pro is doing as changing the theme worked, but we use both these plugins very minimally.
Where are you actually using the cost estimation form? Does WP_DEBUG give you any errors or warnings? Is there any way you could get a mysqldump of this database?

#12

It is the first time I have used WP Cost Estimation. Forms are embedded in any page with “Tax Returns” in its title and also in the private “Form preview” page.

WP Debug is just throwing this error:

[08-Dec-2022 10:28:09 UTC] PHP Notice: Undefined variable: num_pastdue_actions in /home/philipgu/public_html/staging.philipgurnhill.co.uk/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_AdminView.php on line 194

I have a copy of the database in *.sql format, but not sure how to get it to you!

#13

Media library will work as your site is http authenticated. I can delete the file after I download.

#14

Hi @charlie, I have uploaded the *.sql file as a .zip to the media library. It would not allow it to be uploaded unzipped. I hope it is useable for you.

#15

Great thanks, this helps a lot. I’ll let you know what we figure out.

#16

Well I can recreate now, and tap into something wpforms does to fix the rest issue. However I feel like you’ve got a permission issue somewhere with custom post types. Maybe wpforms doesn’t jive with custom WP prefixes. The post type that is failing is wpforms with a capability type of wpforms_form if that helps. Does this happen with administrator privileges as well? I’ll sleep on my fix, worst case scenario I send you my add_filter. I am curious if this is happening to anybody else.

#17

I am really glad you have been able to make progress! From my perspective, this website is a default:

  • WP installation
  • Pro installation
  • WP Cost Estimation installation as a Pro extension
  • WP Forms installation as a Pro extension
  • No custom post types of any sort on the website (unless plugin created)

As previously mentioned, this is my first ever use of WP Cost Estimation, whereas I am now using WP Forms on all websites in preference to Contact Form 7.

I hope this helps!

#18

Wish I could tell you more here. Something with wpforms causes the current version of estimation form think it’s in an archive and at some points changes the global post id. Even bypassing the rest issue this will cause every page you edit in Gutenburg to be the latest wp form you created. It’s very strange, I can turn off nearly everything in pro and still get this issue in your site. I’d recommend for now to turn off estimation form when you need to enter gutenburg or use the classic editor. In estimation I’ve pin pointed the method that is causing this issue (conditionally_add_scripts_and_styles), however the solution might be to send them code so I can’t really give you a time estimation.

#19

Hi @charlie, thanks for all your time investigating this strange issue. I guess WP Cost Estimation is one of the least used bundled plugins, so the problem may not have come to light before now. I hope sending the code to the WP Cost Estimation developers will secure a permanent fix. In the meanwhile, I will deactivate the plugin each time I need to access Gutenberg!

1 Like
#20

not really related to the beta, but my experience of working with WP Cost Estimation software (with pro) has been less that good. hard to explain, but in general it seemed both buggy and caused users issues. I have started removing its use where I can.

I don’t think this is a Pro issue, and more of an issue with the WP CE software

1 Like