Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Actually I don’t think the users are entirely to blame.

    Some of the fault lies with we the programmers. Too many of us have given our code away (which is good) but then also given away free support (which is bad). Giving support away is bad because it devalues us and programs the market to expect support for free.

    Every time someone gives support for free they make it that much harder for the next programmer to charge for support.

    Over the last decade we have educated our market to believe they are entitled to free support to go with their free software.

    Its going to take a lot of re education to get the market as a whole aligned with a paid support model.

    What makes it worse of course is not only do many feel entitled, but they also feel they are entitled to be rude when asking for free support

    +1 davidryal

    So someone has generously given you free code without warranty, and you see it as their responsibility to also give you free support for it.

    Does that about sum it up?

    It looks like its a PHP memory limit issue, raising the PHP memory limit solved the problem.

    It also happens with quite a few combinations of plugins, and when W3 TC is not in use so its not specific to this plugin.

    Sorry, meant to come back here and post that earlier once I had figured it out but totally forgot in the start of year rush.

    I am seeing the same or nearly the same.

    So far I have had the problem with 2 plugins

    When I run w3-Total cache and Gravity forms together, everything is fine. But some plugins when added to the mix cause the white screen of death.

    so far I am able to duplicate this with the WordPress Database Backup plugin and the WPaudio plugin.

    Activating either of those plugins when W3-total and gravity are both running causes a fatal crash. Running those plugins when either W3 total or gravity forms – but not both – are running is no problem.

    It only happens when both W3 Total and gravity are running.

    This is duplicable on a vanilla WordPress install running twentyten

    Thread Starter ashgoodman

    (@ashgoodman)

    Thanks Tom

    The update now allows the setting to be saved without giving an error message but the message: “AWeber Web Form requires authentication. You will need you to update your settings in order to continue to use AWeber Web Form.” still appears above every page and the widget either never finishes loading or gives an error: “An error occurred while loading this control.”

    If your category or archive page, or any other page is set to show excerpts instead of the full content the add this button will not show.

    This is bad enough, but rather than just not showing, what happens is the raw code that powers the button shows. So no graceful degradation here.

    The simple fix for this hat can edit their theme files: switch the_excerpt for the_content.

    It is really disappointing when a company like addthis releases something half finished like this. When a freelance developer makes a plugin in his spare time, fair enough bugs are to be expected, but when a company releases a plugin with major flaws, thats just laziness and poor attention to detail.

    This is part of addthis.com’s business strategy: it ought to be done right.

Viewing 7 replies - 1 through 7 (of 7 total)