Forum Replies Created

Viewing 15 replies - 31 through 45 (of 69 total)
  • Thread Starter JohnRoyce

    (@johnroyce)

    Well, this is the issue I’m asking for help with. When I try to save the Page Access Token it gives the message:

    error: Something went wrong (trying edit feed).

    Thread Starter JohnRoyce

    (@johnroyce)

    Yea! That solved it exactly!

    Thank you for helping out so much, especially since it was not even Spiffy Calendar’s issue.

    (Looking for a tip jar…)

    Thread Starter JohnRoyce

    (@johnroyce)

    When I first set up the plugin a few weeks ago, it immediately pulled in the facebook posts; it hasn’t updated since. But the (old) posts are displayed nicely.

    You can see them on the live site (www.clean-round.com) … farthest right column.

    Thread Starter JohnRoyce

    (@johnroyce)

    Thank you for the information and resource, and the quick response!

    I followed the page’s instructions, and now the facebook feed on the live website has stopped showing an ‘application limit’ error message at the top. !

    However when I try to save the Page Access Token it gives the message: error: Something went wrong (trying edit feed).

    The explanation was problematic for me. Once a version is released, it should not be changed. Otherwise opens the door to coverup and other mischief.

    “For example, when a new version of WordPress is released, they might change the indication of what version number the plugin supports.”

    This breaks the information chain. The industry expectation is that you will issue a new version number if the file changes. This is basic. Why even have version numbering then. Seems a very slippery thing to normalize.

    So what if you make a spelling change–it’s a new version. One without the error. If such small, discretionary, but untraceable changes are normalized, what is to stop a hacker from just making a teeny little change to a URL or php file? It would be much more difficult to stop that kind of fraudulence, made worldwide through a plugin, than it is to simply enforce versioning.

    Wordfence has it right in this case, I think. Yes they are over the top and don’t separate out real issues before blaring an alarm. It’s an irritating way to handle it–but they are following industry norms.

    I agree with Paul and also would have liked to know the link too. I’m glad he said something.

    Wordpress owes its existence to the idea of community contribution, so it seems it would be more consistent with the organization’s stated values to plainly disavow any claims about outside links but allow them.

    It would make this resource for users much better. Why the wall?

    Thread Starter JohnRoyce

    (@johnroyce)

    A browser refresh cleared up the limbo email … I can find a way to fix the other issues. Thank you, it seems like a nice plugin. It’s surely useful for many.

    We’re not talking about new features or enhancements, but simply fixing a prior bug that was sold to users.

    I realize that, in most situations, once you stop subscribing to a product you are no longer entitled to receiving updates. This makes sense … in normal situations.

    Except that Elegant Themes Divi is NOT LIKE NORMAL wordpress themes that you can deactivate … a complete page by page redo of your entire site is required. This is not normal for wordpress, nor is it explained to the less-than-technical designer community ET (and wordpress) claims to serve.

    Complete reconfiguration of a website is not easily doable once you’ve invested your website budget of time and money … and so we arrive at yet another oddly wordpress-enabled scam. Elegant Themes works to force alienated users to pay ransom on what they already paid for: it is blackmail. I will not pay a cent to them.

    Frankly, sadly, the wordpress ‘community’ seems a bit of a hoax at this point. It has for some time now allowed merchants to appropriate the good work and reputation of its contributors, and a poor change of image is happening as a result. Deservedly so.

    I would not have trusted this ET operation if it were not associated with WordPress … sponsorship of such shady business practices deters loyalty in the extreme. Poorly done. Very poorly done.

    rseigel makes a good point: “I’m REALLY pissed at ET for using sloppy code in the first place. They should offer a free upgrade for those of us that aren’t currently paid-up members. This is clearly their fault.”

    The Elegant Themes rep somehow didn’t actually answer the question, that’s how you can know it’s really them.

    WHAT ABOUT CUSTOMERS WHO PREVIOUSLY PAID FOR YOUR DIVI PRODUCT? Could you include a link to the patch for those customers … maybe it is in the blog post you should have published? I missed it somehow and had to spend another hour+ of searching for ET fixes, it is like old times again.

    BTW: “Just make sure you are using the latest version of Divi” is the kind of Orwellian marketer-teflon speak that has helped cause such deep revulsion among former customers who have come to know Elegant Themes too well.

    Paul, you are active and helpful with support in my experience … but this doesn’t really help so much. The email messages are not clear to non-techies. This is not to disparage the plugin itself.

    Maybe if this is important for the plugin’s development, there could be a facility to help point out these maybe-sinister file changes? It’s probably not workable, I don’t expect that, but please note that it is disturbing for the unwashed, like me, to find alarming email and not really know how to move forward. Googling commences, time taken, confusion reigns …

    There is an underlying issue of trust going on as well, which should be recognized. It looks a little corporatoid to ‘warn’ users about something and then offer your service to eliminate the problem, while leaving it to them to determine whether the ‘warning’ is consequential or not. I am not saying this is meant to manipulate users, surely it isn’t, but big tech has waylaid enough folks that an eye to consideration of user time and effort is probably becoming a necessary practice.

    Thread Starter JohnRoyce

    (@johnroyce)

    Thanks Mizagorn for exampling the conduct (ie, babbling your gedanken fantasies instead of exercising your mind and addressing some honest if hard-earned feedback). Of Randy can be said less, it is the general tone of dismissal you get from many techies and who cares.

    I originally gave a one-star because that is about all that can be done now to bring attention to a problem, as Elegant Themes is scamming the community ethos while hiding within a private commercial construct. Many folks have spent their talents and efforts to build a community that is simply treated as something to take advantage of.

    I am glad two other bros joined in to attack a beleaguered customer on behalf of abusive business practices, because it is a chance for customers to see what some techie-types really think about them. I am not angry for no reason.

    That all said, having offered my reasons, I’m capitulating on the 1-star review, because expecting developers to think about others or adhere to a social compact is clearly out of their competency zone. It isn’t fair to the plugin developer to rise above industry attitudes and take responsibility for his development choices as they affect the greater community.

    I did some testing within the ET framework, it doesn’t break things and didn’t give me the suffocating-in-perfume feeling that the premium product perpetrates. If you are sucked into the ET experience, trapped like a fly trapped in amber and being ritually slimed by their support … this plugin won’t make it worse.

    Thread Starter JohnRoyce

    (@johnroyce)

    This is not a bogus review. I’m doing potential users a service, giving a point of view I wish I’d had before getting involved with ET altogether. This ‘free’ plugin is part of the ET ‘platform’ and its position here encourages and gives implicit sanction to that product.

    ET and its developers USE the non-profit WordPress community for personal profit … while using that unfortunate dynamic to be unresponsive to those same users.

    Mizagorn asks, “Why take two years to leave ET?” … while probably also knowing that ET is the Brea tarpits of themes. I’m trying to offer feedback, which is different than just herding users onto platforms for personal gain.

    Thread Starter JohnRoyce

    (@johnroyce)

    The ET experience continues. Mayur, your plugin relies on and directly promotes premium ET themes … yes, the experience you tout is relevant to would-be users. This plugin uses the ET name and encourages its use, and encourages a facile view of a very proprietary system. I am giving the review I wish I’d been able to read before getting involved with it.

    There is a disingenuous element here too, because you know I cannot otherwise give feedback to customers: ET keeps itself apart from WordPress except to use its platform and customer base. Developers should be somewhat in tune with and take some responsibility for what they are doing, or trust is further eroded.

    I request the WP team to observe that this is how the ET team works … shutting down comment through back channels to keep injured users from helping warn others. This is a COMMUNITY endeavor with many, many contributors and I see prioritizing privatization schemes as a violation of that effort.

    Thread Starter JohnRoyce

    (@johnroyce)

    I did rate the plugin (5*’s) back on 3/28/14 … good work, the plugin and support have been exceptional!

    I plan to send google a strongly-worded email, LOL that’s significant … if there is anywhere I might post about google’s feed issue that could make any difference, please let me know.

    Thread Starter JohnRoyce

    (@johnroyce)

    I appreciate the information! Google bought and discontinued Feedburner, so maybe they don’t like rss all that much … seems a strong recommendation for rss.

    Thanks again for the file that turns off Google News images, Allen. It will help us work around it.

Viewing 15 replies - 31 through 45 (of 69 total)