Learning experience is probably needed so that when problems occur, if they do, they have some idea of where to go or what to do.

My last upgrade: VB3.5.0 to VB3.5.4
This sucks :D

I try and use "Auto" as much as I can to stop reinstall of template edits after a VBCORE upgrade. I hate to re-edit templates on hacks installed because of a needed "revert" of a templates.

K.I.S.S. :cool:

[high]* Zachariah goes back to code cave.[/high]

Leaaaaaaaarning Experience!

Hehe. I'm guessing you voted for "Just give me a working modification with a clean install, no template or file edits needed."?

Indeed. You never learn how to get up unless you fall down.

Not sure.

hehe...ain't that the truth! You ought to try doing it for over 40 skins each time vb upgrades O_o

That can't be to fun!

I prefer a learning experience using information given and trial and erorr in order to learn more

Doing stuff like that gives me a greater sense of accomplishment. I love adding hacks,template edits, and doing file edits. It helps me to learn. When something goes wrong I can generally find out what's wrong and fix it. I don't want to burden the coder of the hack I need help with. :D

This is actually misleading ... you should explain in detail so that everyone knows the pros and cons..
what he means here is that a plugin is created (for a product) that will "search and replace" a specific string within a template so that you do not have to do manual template edits

PROS:

1. You will not have to do any edits - just upload the product xml file and you are finished.
2. Coder's don't have to worry about supporting issues such as template editing.

CONS:

1. Coder is assuming you're using a default vbulletin style (at the extreme level, a style that has been modified slightly).
2. Coder is assuming that you will not add a product that will clash with their product. Coder is assuming you will take care of this problem on your own if this does happen.
3. Each time "search and replace" has to run it will use cpu resources -- this will happen each time templates have to be cached. Why use resources when they could be avoided?
4. More Plugins are required to do such edits ... do the math ... if you have about 100 products installed that's 100 more plugins that are not needed (increase memory usage).
5. Creating / Adding a new custom design will take longer (increase cost)
   • Templates are not edited directly; so, you will NOT be able to see the changes on your style/template ... all changes are done at run-time when templates are cached
   • A designer will now need to know how to edit the plugin for each product if necessary. Do they know how to edit XML files or PHP? If not, you will need to hire someone that does.
6. One product's "search and replace" could hurt how another product is displayed or worst how the entire site is displayed.
   • Searching for the cause of problem will take longer as you now have to look into the plugin not the template. And, if you don't know XML/PHP ... you may need to hire someone who does. (increase cost)

As you might have guessed already, I prefer NOT to use the "search and replace" method. Yes, it may mean that I will get the usual template edit questions. But, at least I know I will not be the cause of any of your troubles later on.

For the adminsitrator (non-coders) who prefer the "search and replace" method ... you will be better off doing it yourself or paying someone to do the manual template edits than to pay someone to find the cause of your troubles. Which do you think will cost more in the long run?

Right now, there are only a handful of products that use the "search and replace" so you may not encounter problems as often. However, this number will only increase in time. Hence, so will your problems.

Information provided here is just to provide you with more information so that you can come up with your own conclusions.

With that said, I do understand why coders would want to use the "search and replace" method. At times, I feel like using it myself. :)
0