Mountain Man

So is the plugin compatible with LearnDash Notifications or not?

Your plugin page on this site says your plugin is compatible with LearnDash Notifications. Is it compatible or not? Shouldn’t you know if it works with LearnDash? Your site says it does?

So does it?

Or does it not work with LearnDash?

@yeisonbp the error is happening because the tickets I am trying to import contain “custom fields” from HelpScout. I was able to create a test mailbox in helpscout and I created a new ticket and was able to import that ticket with no issues.

It appears that your importer plugin does not know what to do with custom fields that are part of a ticket in helpscout? In my setup the custom fields are useless and I would like to drop them entirely. I believe that you need to modify your plugin to either drop the custom fields from help scout or allow the user to select what should be done with custom fields that are part of tickets in help scout.

Can you please provide me with some type of a code modification that will allow me to simply drop any custom fields that may be associated with any tickets that are in HelpScout?

@yeisonbp I have tried getting a new token numerous times. It does not seem to make any difference. I continue to get that error message.

In our HelpScout, we did have custom fields setup. Could it be possible this error is occurring because the importer sees those custom fields and does not know what to do with them?

We no longer need the custom fields. So it would be fine if WPAS just disposed of them.

I do not have access to the error log. It should be very apparent when your developers try to import from HelpScout that it is broken.

I cannot offer a screenshot as it will show our company branding on it. Just make an attempt to import a ticket from HelpScout. Any ticket. It can be as many as just one… You should see the same error.

This issue appears to be isolated to helpScout only and not ZenDesk. I was able to create a test account on ZenDesk and was able to import sample tickets.

I am trying to import approx 1,200 tickets spanning from January 1, 2018, through June 15, 2021.

I am not getting the following PHP Error when I try to import

Undefined property: stdClass::$status

Please advise

After I add the API Token from HelpScout, then click on Get HelpScout Mailboxes… I am presented with the error below…

An error occurred during the import process.

Help Scout could not authenticate your request. Check your credentials above. [Error Code: 401]

I have followed the instructions exactaly. I am able to execute the “Get Authorize” from HelpScout. I am not able to continue past this point. The button on WordPress is dead. It is non-clickable. This is some kind of an issue with your plugin.

I could not proceed further than the point described above. I even asked my DevOps to have a look and he also said the function is broken.

Please advise what further steps I can take to get this plugin to work…

Hi @ds123,

Unfortunately, a lot of the functions that our developer had to build into the Stateless plugin to enable it to function on GAE was actually done in a separate plugin that we maintain in-house that overrides some of the Stateless functions. Its a fully custom solution that our developer built for our setup. So, it wouldn’t really be possible to share this with you, because it wouldn’t work on your site.

My advice is to have a developer who is very familiar with PHP go in and build you a custom solution that will enable your theme and other functions within WP to work without uploading to your /uploads/ directory.

Sorry I couldn’t be more helpful.

Hi MB-Jan,

Thanks for the detailed post. I really appreciate the time you took to share your pain points with us. We noticed all of this. Our outcome was that we eventually dumped the Google GCS Plugin and are using WP Stateless. Luckily for us our developer was able to modify some of the plugins that had dependencies on the WP Media Uploads folder. Unfortunately, we do lose some native WordPress Uploads functionality but we really didn’t have much choice because we invested so much money in App Engine DevOps that we just stuck with it.

My hope is that WP Stateless will become more widely used and thus more developed. It would be great if Google were to figure out a better solution for the native GCS plugin. Because we’d rather use that. But the amount of load time that it added to our website was absolutely abysmal.