kennethrg

I gave up trying to get the ads account working and just canceled it, since I had no plans to buy ads anyway. The plugin seems to be working ok at the moment otherwise.

I did see one quirk regarding shipping fees, though. A Google shopping listing was showing an incorrect shipping fee, and I couldn’t figure out how to fix it. Google says shipping fees are managed via the API, but the plugin doesn’t seem to have any settings that would explain how it’s passing shipping fees through. So I might switch yet.

Another plugin I’ve had good experience with is WooCommerce Google Feed Manager by?WP Marketing Robot. It was a little quirky to set up and took some trial and error to get the feed in the right format, but it’s been working well for a couple years for a different WooCommerce store I work with.

Alex, Thanks for the update. I haven’t seen this issue recently, so I think it’s been resolved!

Amber, that’s great to hear! Without knowing how the technology works, I suspect analyzing the page via JavaScript may have some benefits, if for some reason the published page renders differently than what the PHP functions would provide prior to publishing (e.g. unusual page builders, plugins, or other alterations to the page content).

I am always happy to see good tools that promote a more accessible web.

Thanks! This is very helpful. I hadn’t thought of separating “boost” from “reblog” but I see that it makes sense. And going directly to the editor from the reblog is a huge help in this circumstance.

I have been mulling about this too, and with this pull request directing me to the code involved, I have a couple other ideas that may be useful to others:

• The actual formatting code for the reblogged post is hard-coded in the reblog function of class-frontend.php. One could simply change these lines, e.g. div instead of blockquote, and add a custom class.
• It may be helpful to include these as a translatable string, or a string stored in wp_options or something like that; I see potentially four strings that define the formatting of the post: reblog-header-prefix, reblog-header-suffix, reblog-body-prefix, reblog-body-suffix.
• The fanciest way to make this customizable would be to create an editable template for these posts, so the entire thing could be designed to suit the individual site. This template would include shortcodes (or something similar) that would be replaced with values of post_title, author, and post_content by the reblog function when an individual friend post is reblogged.

If I get ambitious later this week, maybe I’ll try to write some code for this PR that will implement some type of editable template.

I am not sure if this is exclusive to the first pull of a new feed, but that’s where I usually see it. I just subscribed to a feed on a recent installation, and almost all of the posts are duplicated. I looked in the database and the posts are duplicated there, once with post_author = 0 and again with post_author = 1. I don’t see any duplicates in the original feed: https://votingaccessforall.org/feed/

I am running Friends Version 2.9.1.

Running 2.8.9 now and I can confirm that the reblog button now creates a new post. However, that new post has a blank title.

Thank you for saying this. I am seeing the same behavior. I was wondering if I was even understanding what “reblog” is supposed to do! But it looks like it is not working right (at all), so that’s obviously part of my confusion.

Mark, thank you for your help. Cryout Serious Slider was indeed creating the conflict. Without that plugin, the forms seem to work well.

In case anyone is following along, here’s the custom function I added to conditionally load all these scripts only on the search page. The function my_algolia_footer(), not shown, simply echos the javascript code from instantsearch.php as Michael described.

function my_search_conditional_loader() {
    if ( is_search() ) {
		add_action( 'wp_footer', ‘my_algolia_footer' );
		wp_enqueue_style( 'algolia-instantsearch' );
		wp_enqueue_script( 'algolia-instantsearch' );
	}
}
add_action( 'template_redirect', ‘my_search_conditional_loader' );

Fantastic! Yes, this seems to work. And just to clarify, I’ve set the plugin to “Use Algolia with the native WordPress search template” so that it uses the modified search template in the FSE theme, not the instantsearch.php file.

This solution obviously still involves some custom coding, but at least it lets me use patterns and so forth for the layout and styling from within the Site Editor, so that’s a great improvement. Thanks!

Michael,
Thanks for the update. Yes, the PHP template file is great for use out of the box, but it necessarily requires customization to work with a theme. One idea I had was to simply copy/paste the HTML from the instantsearch.php file into a Custom HTML block in my search template, but that failed readily, probably because the javascript was not duly enqueued.

Theoretically there could be a “Algolia Search Results” block or something like that, which could be put into a FSE page or pattern. That could be elegant, but it’s hard for me to guess whether or not it would be ideal.

I look forward to seeing what you come up with.

Well it looks like the problem is some bizarre behavior of Cloudflare. I had a hard time believing that this is really what’s going on, because it seems like it would break a ton of stuff, but evidently Cloudflare is removing the “date” header from requests. The ActivityPub plugin uses the date to verify the signature of incoming requests, and without it the plugin fails and does not process the requests.

I was able to create a workaround. It’s not at all pretty. I added a custom Cloudflare rule to add an additional header (“x_date”) containing the current timestamp. Then I added some custom PHP code to check for a missing “date” header and recreate it from the “x_date” header. With all this, the plugin appears to work.

It’s hard to call this resolved, but if we can say that the plugin is incompatible with Cloudflare then I guess it is.

Update: my website is being proxied through Cloudflare. If I completely bypass Cloudflare it seems to work. But even when Cloudflare is passing the request through directly (i.e. no cache) it seems that something is lost which creates the error.

Hi,

I have been using Events Manager alongside Polylang for a while now. I was not aware of this issue. I think I must have stumbled on a workaround by using a custom events page. That is, I created my own page containing a shortcode that displays events. I did this because the client wanted options to display content other than the events calendar/list, but if it also facilitates Polylang compatibility that’s great. That said, I have not fully explored translating the calendar and events, but at least it doesn’t crash.

Incidentally, I run another site with Events Manager and TranslatePress with good results. This translation plugin uses a completely different architecture than Polylang, so that may be another option for you.

Yes, I think this problem is likely related. On one of my sites that uses the calendar view, no events show, just the date number. Oddly several other items on the calendar page (e.g. “today” button and current month name) do not show either. I downgraded to 6.4.3 to make the site usable. I have not fully debugged the problem, but I think it is a CSS issue related to the “fix” to allow the calendar to be responsive. I am hopeful that there will be a resolution from the developer in the next release.