platowynne

Please note the ‘d’ being appended at the end of the URL:

Loading failed for the <script> with source “https://friendsofmaclaygardens.orgd/Web/Plato/PWC_Clients/Maclay/wp-content/plugins/flagallery-skins/phantom/js/phantom.js?ver=1.0”.

Setting the posts to the default p= links gets them all working but this is not what the client wants…

The problem continues unabated. I have deleted and recreated posts using a different title each time to see if I can get them working so here are some links that I wish someone would take the time to look at.

WORKS: https://personhuffcpa.com/fresh-start-for-taxpayers-who-owe-back-taxes/

DOES NOT WORK: https://personhuffcpa.com/file-jointly-or-separately-advice-for-married-couples/ (REDIRECTS TO CATEGORY)

WORKS: https://personhuffcpa.com/prevent-tax-refund-fraud-by-filing-early/

DOES NOT WORK: https://personhuffcpa.com/prevent-tax-refund-fraud-by-filing-early/ (REDIRECTS TO HOMEPAGE)

I have spent HOURS AND HOURS combing through bug trac, googling, trying to read the code to see what might be causing the issue but I am not a good enough programmer to be able to figure it out. PLEASE HELP!

It is very frustrating and random. A post may or may not work and I can’t tell what the difference is between the ones that work and the ones that don’t….

The problem continues and is extremely frustrating. I am thinking it is related to the security updates made to the redirection functions. The posts are redirecting to places that don’t even exist. HELP??

I figured it out. I had to change the height of .timeline .dates in the style_v.css.

Thanks!

@formerfatguy The resource usage is ridiculous. I am caching files and using compression and it STILL uses too much memory and opens too many PHP-CGI processes…..

EVERY one of the twenty or so sites I upgraded to 1.9.5 crashed and burned. I spent yesterday rolling them all back because after several calls saying their sites were down – I checked all of the upgraded sites and indeed, the majority had crashed – White Screen of Death – between the time I upgraded them Sunday night and yesterday. NOT COOL. In every instance, I had to disable AI1EC in the Options table to bring the site back up. Then I had to roll back to the older version, which means the upgrade nag screens are back…..An FYI for anyone thinking of upgrading. CAUTION. CRASH AND BURN AHEAD.

I am going to check into the Spider calendar and see if it is any better. Will report in later today or tomorrow. The upgrading was a TOTAL HASSLE, when I upgraded, it broke my sites right and left and it just eats me alive on PHP-CGI processes. They just got too damn big for their britches. Instead of trying to roll out every feature under the sun, they should have stuck to their basic functionality and optimized for performance. When I went to their forums to figure out why I was getting all manner of error msgs while upgrading, they say they will answer support tix in FIFTEEN DAYS. ORLY? Because if I told MY clients that, they would just leave…..

They will get over themselves when we all start abandoning the plugin instead of upping to the paid version – which, once upon a time, I would have done….

Melissa