reticent98

Now that Buddypress 1.7 has been officially released, I have checked it again and I still get the same error when I try to delete a document. Does anyone elseget the same error?

Fatal error: Call to undefined function bp_activity_get() in ……/wp-content/plugins/buddypress-docs/includes/component.php on line 861

Thank you, agfisio. If I decide to use the Meta Slider again I will try out that code.

If anyone is reading this thread, although agfisio had resolved it before I started replying to it, the theme author fixed my problem by recreating the menus and ensuring that I was using the Widgetkit slider.

So, I restored the header file, then I installed the Advanced Text widget, and switched over to the Widgetkit slider that you use with the demo. I still get the same result. I will contact you with the details.

Hmm. I don’t use that plugin. I had added <?php echo do_shortcode(“[metaslider id=#]”) ?> to the header file and then adjusted the header showcase padding through the theme. I will try using the Advanced Text plugin that you used.

It seems I can only reproduce the issue on my desktop using Chrome. It doesn’t happen when re-sizing the browser window in IE 10 or Firefox. On my iPhone, the problem occurs using both Chrome & Safari, but not in Opera.

https://dschurchaz.org/testarea/

I use the theme for my members-only website, so I created a testing area. No plugins are installed except for Meta Slider, although Soliloquy slider has the exact same behavior. I have noticed the same problem just resizing the browser window. To a certain size, the menu stays on top, even after the menu switches to the smaller format, but after you get down to around the size of a mobile phone screen, the slider appears on top of the menu.

Did this solution work for you, agfisio? I tried it, and my slider is still on showing on top of my menu in iOS. I also had this problem with the soliloquy slider, so I switched to Meta Slider, and the above solution didn’t work for me using either one.

I have been replying to the development fork thread, but I thought I would jump in here given that I experienced the same problems with:

Message from webpage
Ajax Form Error
Status: Timeout
Error: Timeout
Response: (empty)

I discovered this was an issue with some combination of theme and plugins. I am using Preference, and even though it was designed for 3.5, I can’t get the latest development fork of WPUF to work unless I change themes. I still need to test all my plugins, as well.

I have a development area that I am refreshing right now with a vanilla install of 3.5.1 WP. From testing, the version of PHP doesn’t seem to be the problem, as you stated. I have used both your original 2RRR_4_4 and the removed ampersand version on PHP 5.2 with exactly the same results as I experienced on 5.4 after the modification.

As I have time, I will test in my sandbox with the 2012 theme and add WPUF as the only plugin. Thanks for your help.

The new development version seems to resolve this issue.

Yes, that problem does seem to be fixed. I will resolve that thread. My host does let me change my PHP version back to 5.2, so I will re-upload the latest development version without the changes and test it on 5.2

Well, perhaps making the change that I detailed in the previous post wasn’t such a good idea, although I would have had to disable the plugin if I hadn’t. Now, when I try to add a post, I get a pop-up box:

Message from webpage
Ajax Form Error
Status: Timeout
Error: Timeout
Response: (empty)

This happens in Chrome and IE. I haven’t tested in Firefox yet.

I found one issue for people on hosts running the PHP 5.4 upgrade. The problem is explained here. Basically, the whole site was inaccessible until I modified wpuf-add-post.php and wpuf-edit-post.php to remove the & from in front of the $.

From:

//validate categories
		$post_category = $wpuf_cat->validate( $_POST['category'], &$errors );

To:

//validate categories
		$post_category = $wpuf_cat->validate( $_POST['category'], $errors );

I looked at the Pro version, and the demo is running on 3.5.1, which is promising. Do you know if a standard version will be released with compatibility to 3.5.1? I would be willing to buy the Pro version, but I don’t want to spend the money until I can verify compatibility with my theme, etc.