petefuseloft

Hi @constantcontact Thanks for the speedy reply

This is a staging site that’s behind http basic auth. I’m not able to share that information publicly.

Strangely, the opt-in per-form settings were not visible at one point yesterday while I was working on the site. The opt-in started appearing on all of the Constant Contact forms across the site, without my changing anything. The per-form settings are now available again in the admin back-end. The opt-in is visible on the front-end, on every form, regardless of whether the checkbox is checked.

Since you mentioned that the status is stored as post meta, I checked and saw that there is a decent amount of orphaned post meta in this particular database. Could that cause this type of issue?

Where on the server does the plugin generate an error log?

I just saw that there’s a PR for this in the plugin repo. Closing this issue.

@sterndata – I have these all hosted on two separate Linode servers, self-hosted. The servers themselves were updated right before this happened.

@fahimmurshed – I was updating these sites by logging in to each and running the built-in updates.

Interestingly, each time this happened, I would try again, and it didn’t work. But after waiting about 15 minutes, reloading the wordpress admin, I got the database update screen, and the sites finally updated to 3.5.1. So, all of the sites were finally updated, but I’m still confused as to why this happened.

I just tested this out using the development branch and it worked. It returns _id now.

Thanks!

Hi Justin. Thanks for the prompt reply.

So, I’m using a custom post type “projects,” and, for this specific field, in my node/vue app, I’m using axios to get the following url:

https://site.com/wp-json/wp/v2/projects?_embed

then, for each ‘project’ in a for loop, this is the endpoint I’m using:

project.cmb2.box_id.field_id

@bcworkz I thought this might be the case. Thanks for confirming!

Thanks so much. I didn’t realize that upgrade doc existed in the github page, and I hadn’t renamed the content-partial template to content-alnp.php. that was the reason it wasn’t working. It seems to be working fine now.

Thanks again for your responsiveness, Sébastien!

Hi Sébastien,

Thanks for your reply! Flushing the permalinks looks like it did help with one issue, but I’m still unable to get the new version of the plugin to work with my theme. The selectors haven’t changed and the HTML is valid.

Here’s a live post, using v1.4.11 of the plugin. It works for me, but my client says it’s not working, and we have the same machine, macOS version, and browser versions, so this is causing some confusion:
https://minniechostudio.com/capillaries/

If I update to the current version, it breaks the functionality completely.

In my local environment, with the updated plugin, when it scrolls to the bottom of a post, it appends a #response block, inside of my #comments div, and adds an hr with the correct data-url. If I scroll back to the top and down again, it continues to add more hrs and #response blocks, but after a couple times, the data-url for the rest of the hr tags is “undefined”

I’ve tried moving the comments and post-navigation block inside/outside of the #content and article.post divs and nothing is working unfortunately.

Can you see, based on that page, what I’m doing wrong? I’ve used your plugin and the underlying javascript library several times with no issues, but I’ve been trying to debug this specific problem for two days now, and I can’t get it working.

Thanks again for any assistance.

Thank you for your prompt response to this!

Thanks, @nigrosimone. This appears to fix the issue. I’m assuming this PR is going to be integrated in the next release. Any idea when that will be? I imagine this is breaking for a lot of other people.

@nigrosimone, Thank you.

To be clear, this issue appeared yesterday on Jan 31, 2017, when I downloaded and updated to 0.9.5.2. I don’t see a new update in the www.remarpro.com plugin repository.

The issue was not present in version 0.9.5.1

Any other advice?

Joseph,

Thanks for the quick response! I thought that to be true, but figured I’d ask in case you had some ideas. Great plugin, at any rate. Cheers.

-Pete