Search results for

#GreatBlogCrash

#1 Click this link to see Blog page --> 04/20/2023

#GreatBlogCrash
This was the day after the “technicians” destroyed my Blog with migration, updates and upgrades. It appears to have happened some time after 2 p.m. yesterday.

MjL

#2 Click this link to see Blog page --> 04/21/2023

#GreatBlogCrash
Friday evening and I have finally repaired the Blog enough to put it back online. So far only this month works and mostly just the main daily pages —— so only a few links actually work.

I hope to get the index.bat working again so the crash page should be gone very soon. I hope.

MjL

#3 Click this link to see Blog page --> 04/21/2023

#GreatBlogCrash
I think I have the index.bat squared away. If not and you get this far, let me know what happened for you if it didn’t work right.

The photo captions throughout are completely effed up. From what I can tell they scrambled the EXIF coding when the files were copied to the new system. I can fix them, but it means editing every individual file that has html tags embedded into them. This entire thing is so infuriating and frustrating. It is sloppy and unnecessary. Good Night. I can’t take more tonight.

MjL

#4 Click this link to see Blog page --> 04/22/2023

#GreatBlogCrash
There is so much to do with this poor Blog I don’t know where to start. I guess the best thing would be to get back into posting new content. It will be a while before I get the past days, months and years updated, so I think I will just try to get back into the daily routine and take it a day at a time. Be patient.

MjL

#5 Click this link to see Blog page --> 04/22/2023

#GreatBlogCrash
That’s for sure. From what I’ve been able to piece together the IT nerds decided to upgrade software and migrate server systems without regard to what would happen downstream. I imagine the pushback has been extreme but outsourced foreign IT managers don’t care about our problems. In the process they upgraded all versions of all software. Basically like going from Windows 98 to Windows 11 overnight and so much of the code is not backward compatible.

Stuff I coded 10 years ago no longer works.

The only upside I can see is faster speed and fewer errors.
I suppose that was their only concern.

MjL

#6 Click this link to see Blog page --> 04/23/2023

#GreatBlogCrash
Here is an example of what I have to change:

$calendarlink = “/home/xrnk0be2zfi/public_html/Blog/”;

The part highlighted has to be added to every file link on every page because they restructured the file server root directory by three extra levels and refuse to change it back. Some brilliant IT people decided this “protocol” and we all have to live with it.

MjL

#7 Click this link to see Blog page --> 04/23/2023

#GreatBlogCrash
I think I have fixed all the links for this year’s pages.
I still have almost all of the blue column menu links to fix yet.
This could easily take weeks or months to get done at my pace.

MjL

#8 Click this link to see Blog page --> 05/05/2023

#Turbify #GreatBlogCrash
When my Blog access was initially messed up I started keeping notes and I share a bit of that anger and angst here.

MjL

#9 Click this link to see Blog page --> 05/05/2023

#GreatBlogCrash
It is going to be a long while before I can repair the file path damage. Before the idiots meddled with all the file references, both file storage and Internet links had the same root path so there was no confusion. Now if I need to refer to a file for attributes like height, width, or Exif captions —— I have to add three layers of directory to the query.

So if I want to show the image on the web, the path is:
/Blog/$Year/$Month/$Day/FUBAR.jpg.

If I want to access Exif info I have to use:
/home/xrnk0be2zfi/public_html/Blog/$Year/$Month/$Day/FUBAR.jpg.

Imagine sifting through pages of code to separate this confusion.

MjL

#10 Click this link to see Blog page --> 05/25/2023

#Turbify #GreatBlogCrash
I received an email from Turbify tech support regarding their recent FUBAR and fiasco. Keep in mind, that happened a month ago.

On Monday, May 22, 2023
Hello Michael,

Thank you for your patience with this process.

Good news, we have taken steps on our end that have resolved the issue and you should now be able to see your site loading as intended. The cause for your issue is the error logging on your site triggering resource abuse suspensions. Please review your site and the errors it is generating to resolve them as they may again trigger an abuse suspension if they are not addressed.

If you encounter further issues or have additional questions, please reply and let us know.

Thank you again for your patience with this process. We appreciate your business and look forward to assisting you in the future.

Regards,

Aaron
Turbify Support

My reply the same day (3 days ago)
Could you tell me please what file contains the error logs and what directory to look into? Thanks, Michael

No reply since then. This is very typical of these people. They screw things up for weeks at a time and then blame it on the customer with some scary sounding techno-babble. I hate this crap.

MjL

#11 Click this link to see Blog page --> 10/03/2023

I have been going through all my Blog pages, files and scripts for the past couple months and think I have gotten most of them repaired from the #GreatBlogCrash #Turbify caused. Hopefully ALL is working properly again and if not; Please Tell Me. I found tons of pages from the years 2006 thru 2011 that haven’t been working while I was at it.

MjL