PDA

View Full Version : Problem with Editing/Advanced/Delete/Cancel button on Quick Edit for Posts


itsRahul
11-03-2013, 10:19 PM
Hello, I hope someone here can help me.

I have searched for a few hours on google, vbulletin forums, other forums, and have seen many similar issues but none of the solutions provided have helped me.

I will do my best to describe the steps/events related to this bug/issue.

I have been running vbulletin 4.1.7 without bugs for some time now, until this recent issue.

Note: I have not installed anything to my forums (plugins, products) for a long time and this error is relatively new. However, I did try to upload the vbulletin 4.2 files about a week ago and did not finish the install, so I thought this was the problem. I don't want to do a full reinstall because my database is massive and it takes at least a day of nonstop file chopping and query executing which I am not looking forward to doing (I've had to do it twice before). I cancelled the 4.2 install thinking I'd do it another time.

1. A member of my forums told me that he cannot edit his posts. So I tried with my laptop running firefox 25.0 and when I click the quick edit button, I get sent directly to the Go Advanced edit page. When I tried with another computer with firefox 24.0, I got the bug he described. When quick editing, the 4 buttons (edit, go advanced, delete, cancel) simply do nothing when a user clicks them. There's no message or anything.
3. My host, godaddy.com, has not upgraded to php 5.4, which was one of the possible issues I found in a reply while googling. It's still 5.3 and so that shouldn't be related. (Although, my vbulletin control panel says PHP 5.2.17, is this possibly a problem? I hadn't noticed before, but I don't think it's changed in at least a few months, so it shouldn't be related to this new problem with editing.)
4. I've tried creating a new style without a parent, and the bug remains while browsing with that style.
5. I've tried re-uploading from a backup of a month ago. This should have undone any problems from the unfinished 4.2 install files, because I uploaded an entire new directory with the backup and tried running the forums from there. It didn't fix the error.
6. Quick reply, quick avatar edits, mood message, and other small AJAX (I think AJAX) related things are working fine. It's just the quick edit button functions.
7. I tried disabling partial and all AJAX related products in the options of admin cp. Neither had any effect on the issue. I also tried disabling all plugins with the disable hooks line of code from some other solutions thread I found, but it didn't help.
8. I am pretty sure it is AJAX based on my limited knowledge about it, but I don't understand why only the quick edit is malfunctioning if it is a blanket problem. I haven't edited any code in my forum config or functions or any integral file so I don't know if it's a code error either.
9. After the attempt to reinstall 4.1.7 and then quitting when I found out it wanted me to wipe my database, my ajax chatbox on the forum homepage stopped showing. So I re-uploaded my backup forums again to a fresh directory.
10. I have the forums up with that backup (no edits in the last month). But it has the quick edit bug. Everything else seems to work fine.
11. I ran diagnostics which showed that there's no AJAX Unicode Issue with mod_security. Not sure what that means but it said No.
12. I heard about reverting templates (not too sure how to do this effectively), but my recent edits in my styles and templates show dates in 2012 and 2011. I'm ruling that out because that doesn't seem like it could cause an issue now.

Please guide me in the right direction. I don't understand what it could be and I've searched quite a lot.

Max Taxable
11-03-2013, 10:58 PM
Just a hunch, but try re-uploading your clientscript folder from your original 4.1.7 package.

itsRahul
11-03-2013, 11:00 PM
Just a hunch, but try re-uploading your clientscript folder from your original 4.1.7 package.

Would this be different from my full directory upload? Or do you mean a fresh clientscript folder from a new 4.1.7 download on vbulletin?

And, if I do re-upload the fresh 4.1.7 clientscript folder, will it require me to reinstall anything afterward or will it possibly work with just a re-upload?

Also, a user has reported that the smilies button doesn't work either. It seems okay for me on firefox 25.0 though.

Max Taxable
11-03-2013, 11:04 PM
Would this be different from my full directory upload? Or do you mean a fresh clientscript folder from a new 4.1.7 download on vbulletin?

Also, a user has reported that the smilies button doesn't work either. It seems okay for me on firefox 25.0 though.All of these sound like they are javascript related, so my suggestion is to yes, get a fresh cleintscript folder for your version and upload it, allowing overwrite. Can't do any harm, and might just fix the issue.

You shouldn't need a new download if you still have all your folders and files from your original package.

itsRahul
11-03-2013, 11:14 PM
All of these sound like they are javascript related, so my suggestion is to yes, get a fresh cleintscript folder for your version and upload it, allowing overwrite. Can't do any harm, and might just fix the issue.

You shouldn't need a new download if you still have all your folders and files from your original package.

Okay I will try an overwrite upload of just clientscript (I feel like I did try this earlier but I'll try it again anyway). But I was asking, should I use a fresh 4.1.7 clientscript folder from vbulletin or my backup from about a month ago?

ForceHSS
11-03-2013, 11:16 PM
A fresh one is best

itsRahul
11-03-2013, 11:21 PM
Okay I reuploaded a fresh clientscripts folder, and nothing has changed. Those four buttons still don't respond. I tried clearing cache and restarting my browser as well.

I'm guessing my firefox 25 is causing me to go straight to Go Advanced when I click edit, but that's not as big of a deal for now.
Edit: Just tried Chrome and it also goes straight to Go Advanced, weird.

ForceHSS
11-03-2013, 11:48 PM
Have you any plugins added to Firefox or the other guy that might be causing problem. Try disabling all plugins on Firefox if that does not work upload all files (vb version 4.1.7) from the pack that you can get from the members area and run upgrade.php but first delete the config.php.new and the install.php files

itsRahul
11-03-2013, 11:53 PM
Have you any plugins added to Firefox or the other guy that might be causing problem. Try disabling all plugins on Firefox if that does not work upload all files (vb version 4.1.7) from the pack that you can get from the members area and run upgrade.php but first delete the config.php.new and the install.php files

You mean for the quick edit redirecting to Go Advanced page right? I haven't bothered looking much into this because I'm more concerned about fixing the edit button for everyone.

ForceHSS
11-03-2013, 11:56 PM
Then reupload all 4.1.7 files and run upgrade.php as you said in your first post you uploaded the 4.2.2 this could be the cause of all your problems so running the upgrade.php might help. There are some files you should remove, the ones that don't belong in 4.1.7 that are in 4.2.2 as default but to do that you need to go though each version and check

itsRahul
11-04-2013, 12:33 AM
The thing is, I tried to upload the new 4.2 files at least a week ago, and the first editing-related problems have occurred only today or yesterday. I'm typically posting daily and occasionally editing and did not notice any issues until very recently. So I'm not too sure that it's related to the upgrade. After all, I'm currently running on the backup that I saved before attempting any installs a week or so ago.

ForceHSS
11-04-2013, 12:34 AM
it would not hurt to try

itsRahul
11-05-2013, 10:16 PM
I've upgraded to 4.2.2 successfully, but now am getting some errors. I've looked around, again, but I can't seem to find a good solution.

In every page, I get 2 warning errors:

Warning: Non-static method THANKS_CACHE::init() should not be called statically, assuming $this from incompatible context in ..../dbtech/thanks/hooks/global_start.php on line 9

Warning: Non-static method STATUS_CACHE::init() should not be called statically, assuming $this from incompatible context in ..../dbtech/status/hooks/global_start.php on line 9

At AdminCP I get the warning errors plus:

Unable to add cookies, header already sent.
File: /home/content/94/9082694/html/forum/includes/class_core.php
Line: 5745

So I added the DISABLE HOOKS line in my config.php, which lets me get to the forums and admincp. My edit post ajax problem seems to be fixed. But there's a bunch of notices about outdated templates and failed merges, and I still have the errors related to global_start. Do I need to reinstall plugins one by one to fix this? I've seen other people's similar problems with 4.2.2, but I'm not sure how to resolve this.

ForceHSS
11-05-2013, 10:45 PM
you need to upload the fixes for 4.2.2
post 24 and 26 (http://www.vbulletin.com/forum/forum/vbulletin-4/vbulletin-4-questions-problems-and-troubleshooting/4000233-warning-declaration-of-vbforum_item_socialgroupmessage/page2)

tbworld
11-05-2013, 10:56 PM
I believe if you download the latest copy of v4.2.2 the "class_core" changes have already been implemented.

See this post from @PaulM...
https://vborg.vbsupport.ru/showpost.php?p=2452480&postcount=90

Just in case you have not enabled it :)

ozzy47
11-05-2013, 11:06 PM
The first two errors can be solved by uploading the files for those two mods again. They were patched on here some time ago.

itsRahul
11-06-2013, 03:29 AM
you need to upload the fixes for 4.2.2
post 24 and 26 (http://www.vbulletin.com/forum/forum/vbulletin-4/vbulletin-4-questions-problems-and-troubleshooting/4000233-warning-declaration-of-vbforum_item_socialgroupmessage/page2)

I believe if you download the latest copy of v4.2.2 the "class_core" changes have already been implemented.

See this post from @PaulM...
https://vborg.vbsupport.ru/showpost.php?p=2452480&postcount=90

Just in case you have not enabled it :)

I applied the changes according to these two posts, and the edit function, as well as the forums and admin CP, seem to be working fine. I truly appreciate the quick responses and support from you all, thank you! :)

Now all I have is some template updating to do to fix my skins, and I hope everything else is taken care of now.