November 26, 2018 at 2:40 am #134094
I am having an issue with the Inbound Pro Email component. I am able to preview the email and even see the template in the visual editor, UNTIL I hit save and it gets assigned a /mail/ URL, and then a 404 error gets returned. So once an email is saved, I can’t do anything further, let alone send it.
I am using Nginx without Apache. I’m guessing there is a redirection issue here. Any direction on where in Inbound Pro that I can look to fix this would be appreciated… If you know of an .htaccess fix for this I can convert it to an Nginx directive.
GregNovember 26, 2018 at 3:21 pm #134100
Try this: Head into your wp-admin->Settings->Permalinks and resave these inputs 1x and then check to see if your /mail/ based permalinks begin to work. Most times this routine will fix the 404s.
Hudson AtwellNovember 26, 2018 at 4:06 pm #134103
That didn’t seem to work. Any other thoughts? Do you think this could be a caching or Nginx specific issue? I know both of these things can require tricky workarounds.
I just noticed the same issue with landing pages. Previewing before publishing works, but once I publish the permalinks return a 404. Although I’m aware of a potential Nginx hack to get the landing pages to work (someone posted it somewhere around here), but not for email links.
The CTA permalinks work fine though…
GregNovember 26, 2018 at 4:46 pm #134104
That should have worked. What kind of Permalink structure does your site have?
It could be a caching issue, or a CloudFlare issue if you are running it. Please try clearing all and we’ll see if it helps too.
-HudsonNovember 26, 2018 at 5:52 pm #134105
Ok so made progress here by disabling W3 Total Cache. Permalinks for the emails are now working fine, once I excluded /mail/* from page caching. Easy enough…
For whatever reason though, the visual editor for emails now doesn’t work – it just doesn’t show up at all, but it DID with caching enabled. *shrug*November 27, 2018 at 3:23 pm #134114
Maybe the web developer console has some data about why it’s failing? If you’d like, you could take a screenshot of the console after attempting to load the frontend editor and I could study the result:
The console report is empty, strangely. It doesn’t even appear to be trying to load the editor.
While I’ve got you here, I’m also experiencing an odd issue with one of the templates (see attached image). The preview and web version is displaying some of the code, but when I actually send this email as a test it renders perfectly (at least in Gmail and on mobile). This is the Inbound Now email template.
Oh, I’m still in the weeds on a current development, but WILL get back to you soon regarding the wp_mail project.
Attachments:November 29, 2018 at 4:07 pm #134149
With Visual Editor if there’s just a blank screen then there may be an underlying PHP fatal error we could reveal by temporarily enabling WP_DEBUG. More information on WP_DEBUG here:
Could you link me to a web version of the email for review?December 1, 2018 at 10:40 pm #134155This reply has been marked as private.December 2, 2018 at 10:32 am #134156This reply has been marked as private.December 2, 2018 at 12:58 pm #134157
It appears it only happens when logged in. And I figured our why: our Advanced Custom Fields front-end editor plugin is inserting code that’s breaking the HTML. Turning it off fixes it…
You must be logged in to reply to this topic.