I have been hired to fix a ecommerce website in PHP, and improve the SEO Organic results.
So I've been going through the code, and it's pretty old school the way it's written. The original developer who left the company back in 2007, created a product database, in which he placed all the HTML in the columns in MySQL.
So instead of a column saying "Explosion Resistant Phone" it says verbatim, shortened
And it issues a echo command to output the data above. Basically it's pure PHP with all the HTML stored in the database. All the pages are pure PHP that generates everything.
So my question is
Do you think it's worth the time to fix the database records?
Write a program in something to go through each record, strip out the HTML, decode and encode the text to the proper format, and then update the record?
I think it is, but my friends are telling me I'm crazy to do that. It will take too much time, do the best you can in a very short amount of time. But there's really nothing to work with, it's all in the database.
I really need the flexibility of altering the HTML that the data will reside in for proper search engine results, but writing a program to do this may take awhile and will triple the price of the project.
I want to alter the design to which the pages are static HTML, With containers that call PHP script to populate the items.
It requires more information about exactly what "hired" means and exactly what "fix a ecommerce website in PHP, and improve the SEO Organic results" means to the company (not you.)
and will triple the price of the project.
It wouldn't take me that long to write a program to scrub the data so....
- There is more to it than you described.
- The project is much too short for any feel good enhancements.
- Perhaps you are approaching the scrubbing in the wrong way.
I should of used the word contracted to alter the mechanics of the program code to produce the proper HTML for crawling by search engines.
When I say triple the time, that includes testing the program to scrub the data, and then running it on a test platform, and then doing it on the new production website. I figure 1 day for the data program. Then take the extracted HTML and wrap it back around the data fields, and correct the HTML in the proper format. I can either alter the SQL Export file, or go into the database and alter the columns.
It means more to the company that contracted me, they have 32K products online that they sell, and 26K items can't be found at all in search results, which has resulted in a 80% drop in sales over the last 6 years. People are getting laid off.
Yes there is more to the project than I mentioned. I don't have the entire project code, just the product display system and the files needed to drive it, which is fine.
I haven't written a line of PHP in 6 years, just been doing ASP.net, and I haven't used apache server in 6 years. Plus after looking at the code for about 4 hours, they open a connection to the SQL Server on Apache startup, and never close it (That's what the comments say), won't know for sure until I get the file I need to verify it.
I have a new development machine setup now with apache and PHP, and MySQL, but need to pick out an editor or IDE to work with. Going the write the database program in ASP.net.
Anyways, I'll take that as a yes, strip out the HTML and re wrap it around the data.
That's rather a story for The Daily WTF!
Honestly: throw it away and create it from scratch with proper design.
Also: create some update mechanism that the items on the web site's database and the items in the "normal" database of that company do not differ from each other and that new items are added to the other db automatically etc etc etc...
I get the rest of the files I need today to run the program.
I think I'm going to just strip out the HTML on the fly, and repackage the data, and fix the SQL connector. They have a back end for product mananagement that inserts the HTML when a product is created.
I wanted to start fro scratch, but they want a small fix to see if it makes a difference.
Ok lets agree on one thing , ribbon bars at first glance look pretty cool , but as many switched from excel 2003 to 2007 I bet the novelty ran out pretty quickly.
For all the software planners your there, heres a very basic tip when it comes to using ribbon bars
1. When people are used to how your toolbars are organized its generally a bad idea to switch to a smaller tabbed version where people have to guess.
2. With screens gettign wider and not longer, putting this massive chunk pf space at the top of your app is not so good. big workspace makes for easier use.
My apologies if this rant is a duplicate of some previous one. . . but I just dived into Office 2010 with some course-ware I am going though
Yeah they do , also have your spent more than 5 minutes in a spec meeting and thought to yourself customers kinda know what they want but have absolutely no idea what they need ?!
Eddy Vluggen wrote:
There's always a new hype :->
there is , one person goes metro style the whole planet has to go , I went to tech ed this year , and for the first time try to familiarize myself with windows 8, it took nearly forever to figure things out , for really basic operations. then they did away with the start button. . . I mean seriously !? both apple and linux have implemented this feature and all of a sudden some genius at microsoft believes no its better to have a pane with randomly sized blocks in an unordered list so someone can have fun while looking for their apps.
Now dont get me wrong first glance it looked good. . trendy as they say.
then on first use was like my WTF moment for the year
first feature I installed , to get the start icon back
you can have a splash screen that is animated, a paper clip that pops up and annoys you while you are trying to write a document and you can have an animation a dog sniffing while you are trying to search your documents. but a programs biggest function is to finish a task and not entertain you