avidtrader

Re-upping this in case it was missed two months ago…

Thank you for all of the functionality in this plugin. I have a more specialized need, to display only a targeted portion of another post’s content.

I’m not referring to the first X words of a post,* but to a section of the post’s content. (*However, a solution would be to specify EXcluding the first X words of a post.) For example, can my shortcode specify only the “targeted content” in the following post’s content:

I don’t want to display this text in another post, but I do want to display this <DISPLAY-ONLY-THIS> targeted content </DISPLAY-ONLY-THIS> that is between the tags.

The tag can be static, and not altered on-the-fly. The tag can be limited to only one usage per post, if that helps to identify a solution.

Thank you!

Have you not seen my latest message on this thread? I wonder whether WordPress decided without announcing it that they would no longer send notices of a post immediately. That would be pretty bone-headed and irritating, and unprofessional to make that decision unilaterally and silently. Anyway, any word from you on reinstating the option, so that adults can make their own choice about how to send?

“If you worked with a small list of subscribers, it’s ok to send immediately.”

My sending hasn’t hung the server ever, and I’ve used your plugin for years. Probably it’s because my list isn’t large enough to be a problem. But what concern is it of yours? State a warning, offer a toggle, and let the customer choose what he wants. That’s how I treat my customers, who want IMMEDIATE delivery of the TIME-SENSITIVE information in my emails. Now they can’t, because you thought yourself superior to my relationship with them and with my site host. Seriously, so looking forward to see what other features I might like that YOU decide I don’t need. Sad.

No. Not until I have a degree of comfort that the issues I described earlier are recognized as having contributed to this episode. It’s not possible to assume you’ve corrected them until you acknowledge them.

As I mentioned on another thread in response to your rollback directions, they don’t include instructions for backing up the recipient base, or the templates we have spent so much time carefully crafting. At least the recipients list has an export function. The instructions aren’t updated with precise instructions.

Regardless, totally ignoring this step in the rollback instructions, and its potential impact on the user, reflects how shallowly you even considered the UX. Which probably explains much of the other issues encountered by users, and hardly inspires confidence to trust v4.0.11 won’t make matters worse.

• This reply was modified 5 years, 8 months ago by avidtrader. Reason: potential language barrier

You may be the best coder in the universe. But if you introduced a single new feature or CHANGED/REMOVED a single aspect WITHOUT CONSULTING AT LEAST A FOCUS GROUP OF CURRENT USERS then you made a mistake. Not a coding mistake, which even the greats make, and which can be corrected. A marketing mistake, which can be existential.

You didn’t do that. Don’t claim you did that. Multiple features were suddenly GONE, features that were integral to how so many customers used your product. Did you ever compile ANY use-cases before disappearing the Reports, or the Templates, or introducing the reliance on Cron jobs? (To name just a few.) Has no one EVER asked you to integrate with Mailchimp and others? THAT would have been worth doing.

Preparing your user base for a change, providing a forum for them to communicate about the change, is all SECONDARY to choosing what to change.

So much potentially great software is now gone forever because its creator didn’t realize the product had reached a critical mass of users, and THEY were the ones to dictate changes. You’re not Steve Jobs.

NOW THE IMPORTANT POINT ABOUT MAKING CHANGES THAT CUSTOMERS WANT: Test, test, test.

Clearly, you did not thoroughly test the new version. None of them, I believe. Maybe in 2-3 environments, but not in every permutation of vWP, O/S, device. Not every feature. Sign-ups? You did not test that. WE TESTED IT, EVERY NEW ITERATION. Testing will never discover every bug, but good testing discovers most — before making us suffer the rest.

So, thank you for the product, and for the headaches.

You should stop defending your UX changes. Whatever the “purpose” that was in your mind, you clearly never polled your users. That’s not a mistake. It is unprofessional. And it breaks a trust between us. So, whatever your “purpose,” it was wrong. It is OUR purposes, as users, that should be guiding your efforts.

What is the alternative solution you migrated to?

So, no solution or even notice of coming update to correct the manual sending problem? Or, perhaps you think the controls already exist, in which case, where’s the instructions to set it? You really shouldn’t let an ongoing issue like this persist into the weekend.

Not here. After updating to v4.0.4 and visiting Cron URL, this is the result:
{“es_remaining_email_count”:0,”message”:”PLEAE_TRY_AGAIN_LATER”,”status”:”ERROR”}

This should be a case study for how NOT to roll out an update. At least some benefit to the fiasco.

Not one bit. Because it’s not there.

Reports only lists the posts that have been sent or are still queued, and has a button labeled “Send Queued Emails Now”.

Nothing else there. Nothing anywhere that will allow me to set a default that automatically sends my posts when they are created.

LIKE THE PREVIOUS VERSIONS. LIKE YOUR OWN PRODUCT DESCRIPTION LISTS AS A FEATURE.

This is the only instruction I can find:
https://www.icegram.com/documentation/es-how-to-create-and-send-post-notification-emails-when-new-posts-are-published/?utm_source=es&utm_medium=in_app&utm_campaign=view_docs_help_page

But it is USELESS. It describes paths that my v4.0.3 doesn’t have:

“Email Subscribers -> Templates”?
“Email Subscribers -> Post Notifications”?
“Email Subscribers -> Templates”?

You. Have. Fixed. Nothing.

So, sorry to bother you from more important matters, but WHERE IS THE CONTROL OR TOGGLE TO ACTIVATE “ALLOW TO SEND QUEUED EMAILS”?
Thank you.

May I give you friendly feedback?

After all of this time and all of these problems, you feel it is adequate to simply say “allow to send queued emails is a part of 4.0.3“.

That’s it. You can’t be bothered to add a quick sentence saying THE LOCATION OF THIS CONTROL THAT WE’VE BEEN BEGGING YOU FOR. We’re just further delayed in resolving the situation, which cheapens the solution you spent so much extra time creating.

So, the feedback: Try to do a step more, and not a step less. I suspect the same problem is responsible for releasing the original update without thoroughly testing it first.

Seems like updating WP version helped. At least the report is compiled, as I described above. But still requires manual sending, and apparently the new version promised for today didn’t happen.