There was a major version upgrade done yesterday to the VBulletin forum software. Bugs like this are "normal" after such an upgrade.

FYI, you can still use the quick reply - you just have to hit the button in the first post on the page. Minor annoyance, not enough to get your panties in a wad about, give the PTB a few days to work out the bugs.

 

I'll thank you to keep your comments constructive.

The quick reply and any other problems are likely due to templates that need to be brought up to date. This has to be done carefully & is fairly time consuming, and F150Online is not the only forum I look after. I have already done several of them and plan on doing the rest of them today, time allowing.

About the gallery problems, I haven't had one yet that I couldn't fix by clearing my cookies. This has proven to be true on both Firefox and IE7. I have noticed fewer problems of this kind in Firefox.

 

I have tried multiple times clearing the cookies and still nothing.

Sometimes you just need to leave things alone. I see no reason why the site needed a upgrade, as it was working fine.

But what do i know I am just a little ole member.

 

Updates are a part of life. If you update, you get better protection against security exploits and access to new features. If you don't update, as time goes on, you're vulnerable to more and more security exploits and get no new features.

It is the same with computers. A few years ago, I took an unpatched laptop to the university library. Within half an hour it had a virus. I didn't download anything, but some other person's infected computer had some worm that detected & exploited a security exploit on my laptop.

At any rate, I have fixed the multi quote/quick reply being broken.

 

Sweet, Thanks

I understand updates to protect the site is a needed thing but why would that effect the overall functions. When i update my computer it doesn't change any of it's functions??

And the gallery is still not working

 

When you update your computer, it doesn't usually add any kind of functionality to the user interface. It is almost always to patch a security hole. Every now and then some of the application libraries are upgraded to add new features or support some new program, but this will rarely (if ever) affect the functioning of a program.

With vBulletin, features are added with most new releases, and existing features sometimes get modified to work differently. This usually means template changes. vBulletin does this automatically during upgrade for anything that hasn't been customized. For anything that HAS been customized, it's necessary for the admin to go in and manually copy the customizations over to the new templates. This has to be done carefully, since a small mistake could cause some feature to break, and sometimes the code being copied has to be modified so that it works in the newer version. Quick reply / multiquote was broken by something that worked OK in 3.5.3, but not in 3.6.9. The part that was incompatible took some time to chase down.

As for the gallery, it works fine for me in Firefox and (usually) fine in IE7. If it breaks, clearing cookies seems to fix it. Same for the classifieds. I tested them both after the upgrade, in both browsers.

 

I apologize, but I am just expressing our collective frustration.

As you know, if people don't communicate that there are problems nothing will get fixed.

 

No worries

 

Sorry but that is unacceptable and (Usually) just does not cut it. And i should not have to switch to firefox to make soemthing work that is absurd. I get so sick and tired of hearing that.

And again I have cleared my cookies numerous times and it still does not work and I should not have to clear my cookies any time i want to edit and add pictures to my gallery.

Something is WRONG!!

 

Here is what i get regardless.


EXCEPTION INFO
Exception overview
Error message: The variable "client.gallery_id" is not defined!
Error type: expression
File: /opt/tomcat6/webapps/ROOT/galleries/admin/orderview.cfm
Row: 6
Column: 4

Program code
4 </CFIF>
5
6 <CFQUERY DATASOURCE = "f150galleries" NAME = "getpics">
7 SELECT photo_filename, photo_label, photo_thumb, photo_id, photo_order
8 FROM photo_t

Stack trace
[Error message: The variable "client.gallery_id" is not defined!]
com.youngculture.smith.engine.cfutil.SmithStruct.g etVar(Unknown Source)
__smithdynamic._var._www._html._f150online._htdocs ._galleries._admin._orderview.execute(_orderview.j ava:35)
com.youngculture.smith.engine.pages.CfPage.run(Unk nown Source)
com.youngculture.smith.engine.pages.PageUtil.runPa ge(Unknown Source)
com.youngculture.smith.engine.util.PageDispatcher. includePage(Unknown Source)
com.youngculture.smith.engine.util.PageDispatcher. includePage(Unknown Source)
com.youngculture.smith.engine.servlets.SmithServle t.serviceRequest(Unknown Source)
com.youngculture.smith.engine.servlets.SmithServle t.service(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet .java:803)
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:233)
org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:175)
org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:128)
org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:263)
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyo teHandler.java:190)
org.apache.jk.common.HandlerRequest.invoke(Handler Request.java:283)
org.apache.jk.common.ChannelSocket.invoke(ChannelS ocket.java:767)
org.apache.jk.common.ChannelSocket.processConnecti on(ChannelSocket.java:697)
org.apache.jk.common.ChannelSocket$SocketConnectio n.runIt(ChannelSocket.java:889)
org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:690)
java.lang.Thread.run(Thread.java:619)