Skip to:

Opened 11 years ago

Closed 11 years ago

Last modified 8 years ago

#4850 closed defect (bug) (duplicate)

Upgrading from 1.6 to 1.7 causes post update button not to work.

Reported by: magichew's profile magichew Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.7
Component: Templates Keywords:


I updated long established BP site running BP-Default theme from 1.6 to 1.7. Since the update the Post Update button has been unresponsive. I thought it could be a theme issue as I changed it to twentytwelve so I changed it back to BP-Default and the issue remained. Tried killing plug-ins, no change.
Downgrading again to 1.6 fixed the issue.
I've installed 1.7 from scratch on a few sites and used with the twentytwelve theme without issue.
Could be an issue upgrading from 1.6 installs?

Attachments (4)

Firebug.jpg (125.0 KB) - added by magichew 11 years ago.
POST Tab.jpg (141.4 KB) - added by magichew 11 years ago.
Missing POST.jpg (25.3 KB) - added by magichew 11 years ago.
POST TAB 2.jpg (206.6 KB) - added by magichew 11 years ago.

Download all attachments as: .zip

Change History (22)

#1 @r-a-y
11 years ago

  • Component changed from Core to Theme
  • Keywords reporter-feedback added

Can you elaborate on what you mean by "unresponsive"?

bp-default appends an animated spinning GIF when you click on the "Post Update" button.

However, for theme compat, theme compat uses a subtle, pulsating animation on the button itself. (See #4610.) This might not be as clear as the spinning, animated GIF, but let me know if this is what you meant.

#2 @magichew
11 years ago

Sorry r-a-y. You're right and I did notice that the the button pulses when using the twenty twelve theme and the spinning wheel is visible when trying with the BP-default. I should say that the post button doesn't post. It reacts like it always did and looks like its going to post but the text never gets posted. It just stays in the text box where you can type.

Version 0, edited 11 years ago by magichew (next)

#3 @magichew
11 years ago

  • Keywords reporter-feedback removed

#4 @magichew
11 years ago

modemlooper suggested that I add the buddypress-functions.php file to a buddypress folder in my theme's folder. Unfortunately this had no effect on the problem.

Last edited 11 years ago by magichew (previous) (diff)

#5 @boonebgorges
11 years ago

  • Keywords reporter-feedback added

magichew - Do you know how to use a JS console like Firebug? Could you enable the console, and see what happens when you click the Post Update button? Is it sending a POST request? What's the response code (404, 200, etc)? What's in the response body?

11 years ago

#6 @magichew
11 years ago

  • Keywords reporter-feedback removed

Looks like a 200?

I've attached a screen shot.

#7 @boonebgorges
11 years ago

  • Keywords reporter-feedback added

Thanks, magichew. What's being sent in the POST request? (The Post tab.) You're not getting a response back from BP, which is a bit perplexing; if you're getting a 200 response, it means that *something* should be returned.

11 years ago

#8 @magichew
11 years ago

  • Keywords reporter-feedback removed

boonegorges I hope I've grabbed the right stuff. See POST Tab.jpg

#9 @boonebgorges
11 years ago

Thanks, magichew, but that's the wrong tab. Find the Post tab under Console.

#10 @magichew
11 years ago

I don't seem to have one.

11 years ago

#12 @magichew
11 years ago

Got it. See POST TAB 2.jpg

#13 @boonebgorges
11 years ago

Thanks for the additional screenshot. From what I can gather, it looks like the JS is working correctly. That means that something's happening server-side, which you'll have to debug. Unfortunately, it's not going to be straightforward, as there are several layers where things could be going wrong.

Is other AJAX working in your theme? That'd rule out at least some possibilities.

Any chance you could email me creds for your site? WP creds as well as server creds, so I can try to trace the issue. boone at gorg dot es

#14 @magichew
11 years ago

Sounds way over my head boone. Check your inbox. Is admin enough for you or do you need super admin?

#15 @boonebgorges
11 years ago

  • Resolution set to duplicate
  • Status changed from new to closed

Thanks for the details, magichew. I've found the issue. Moving discussion to #4761.

#16 @r-a-y
11 years ago

  • Milestone Awaiting Review deleted

#17 @boonebgorges
11 years ago

(In [6826]) Improvements in the way ajaxurl is determined

Introduces bp_core_ajax_url() for easier unit testing

Switches bp_core_ajax_url() back to using admin_url(), but now it's more
sensitive to various HTTPS setups, including FORCE_SSL_ADMIN.

Corresponding unit test:

Partially reverts r6790. See #4850.

Fixes #4761

Props r-a-y

#18 @DJPaul
8 years ago

  • Component changed from Appearance - Template Parts to Templates
Note: See TracTickets for help on using tickets.