So….what is the actual solution to this problem. Downloading and uploading via FTP every time isn’t the answer…especially for a “Pro level” plugin.
I’m fine doing that once, but it obviously didn’t resolve the problem. The problem is that the plugin is clearly thinking that my account is expired.
So what are the next steps to actually resolve the issue?
Deactivating and reactivating the plugin did not remove the error message, either.
That did not solve the problem. While the version is updated the error message still persists.
As an update. I think we resolved this by checking the box to disable Frontend CSS. I am concerned, though, that this might impact other areas of our site like our downloads. We applied this in production and left the disable frontend css box unchecked in staging so you can see and replicate the issue through the steps above.
Let me know what I can provide to help troubleshoot.
Hi Nayeem, I don’t think I’m explaining this very well.
We have a staging site that we use to test and update plugins and add content throughout the week. One Fridays, we push those changes live to production.
So, right now our production instance is gaining downloads and the download counts are being implemented. That document in staging might only have 25 downloads. In production, by next Friday the document has generated 150 downloads.
Next Friday, we’re going to push the staging site to production and the number of 25 is going to overwrite the number of 150.
At least, I’m assuming that’s going to happen. We just installed DM and are trying to head off this scenario.
What I would like to do is not push the table from staging that contains the download counts to production, but I need your help understanding which table might contain those counts.
Does that make sense?
–Sean
Awesome!! Both outstanding features. Thanks for continually enhancing the Download Manager and it’s plugins. Appreciate the support getting it going.
Thank you. Did I just miss that in the instructions for setting it up or was it sometehing you added to make it work?
–Sean
Thank you! Looking forward to getting this up and running.
Is there an update on this. You should have received an invite to access and test against our Mailchimp instance.
Thank you Shahjada. This worked to get the modal working and collect email addresses. The modal opens as expected and we can enter an email address. Those email addresses are also visible in the “Subscribers” section of the admin console.
Unfortunately, the email address and name aren’t being added to our Mailchimp audience. We have the API configured and have selected the appropriate list (demonstrating that that API key is correct) but no new entries are visible in Mailchimp.
Can you help us troubleshoot why the Mailchimp add-on isn’t working?
Thanks!
What would be the time required to make those adjustments and, once implemented, would they be fully supported in future upgrades without incurring additional costs?
This still doesn’t work at all. Here’s what I need you to do to see how it doesn’t work:
1) Go to https://birlacarbon.staging.wpengine.com/technical-research-papers/
2) Click the plus sign next to “Carbon Black Fundamental Studies”
3) Click the download button next to “Lock Options Test Document”
4) Note that the page simply opens a new tab and reloads the same page in that tab.
This document has the email lock enabled. We do not use the download pages for the individual documents, which might work for the test document you created, but doesn’t work for our usage of the download button in the Link Template.
Please advise on how to resolve this.
Thanks!
Thank you. Can you help me understand what changes you made so we can replicate them on production?
–Sean
Yep, that seems to have fixed it. We updated in production and set the Bootstrap to 3 and disabled bootstrap JS.
Is there a timing for when all the templates will be bootstrap 4 compatible?