outis

No need for the eval():

	return preg_replace_callback(
		$regex_phrase,
		function( $matches ) use( $encode_method ) {
			return $encode_method( $matches[0] );
		}, 
		$string );

• This reply was modified 5 years ago by outis.

I’ve recently found out that WooCommerce is on github; I’ll turn this into a pull request there.

Ah, I thought Requests and Feedback was for the WordPress software itself, rather than the forums. Thanks for the move.

• This reply was modified 5 years, 10 months ago by outis.

I was not aware the WooCommerce plugin was on github. I’ll fork & submit a pull request there. Thanks.

Thanks for chiming in, but, again, that’s not what I’m asking about. I didn’t plan on creating any new posts related to the held topics, I merely wanted to be able to return to and view the existing posts. Neither the held post nor this is an urgent matter. The other post I mentioned wasn’t directly related to the held posts, it was regarding adding a “preview” function for posts to WordPress forums so that you can see how a post will be rendered without submitting the post, in order to avoid having to submit a post and then edit it (which then triggers moderation).

My question in this thread is whether there are any links to one’s held topics. As far as I can tell, there aren’t.

• This reply was modified 5 years, 10 months ago by outis.

This topic isn’t resolved. How can it be changed back to unresolved?

Thanks for the idea (which I often do), but that doesn’t address my situation. It isn’t that data got lost, it’s that a post was flagged for moderation (which happened after editing it, as I had to submit it to see how it would be rendered; I’ve another topic intended for the forum devs to add a preview functionality) and I don’t see a way to return to the topic page using the WordPress forum’s interface. The only way I’ve found to return to that post is to check my browser history.

Is the developer asking for a WordPress admin account, or some other server admin account?

Depending on where the plugin is hosted (such as the WordPress plugin repository), you might be able to find an older version; there are numerous pages that go through the various ways you can do this.

An opinion: as a developer, if a version of a plugin stops working and it appears like it might be a bug, I don’t treat it as a support case but as a QA case. This comes with a different set of responsibilities for both parties: for the issue reporter, the primary responsibility is to provide enough information to reproduce the issue (but to weed out irrelevant information). If you can do this, the developer should then be able to implement a fix in the next version. In these cases, the developer never needs to touch anything on your server, which is what makes a case more of a support issue. Also, debugging generally requires having more control over a server than you’d get with just a WP admin account (though server access can be helpful in figuring out how to recreate the issue). As for how this applies to you, you can see if the developer is open to this route.

Another option (if the developer is only requesting a fee for screen sharing and not to work on your server) is to set up a new site so that you can safely give them access. In particular, set up just enough to recreate the issue (this is also a way to fulfill an issue reporter’s primary responsibility) and don’t put anything on the site that could be used to compromise another site (e.g. don’t reuse passwords from other sites).

I’ve updated the patch to apply to WL 0.56.

Sadly, the plugin author appears to be MIA.

Glancing over the plugin code, it’s not possible to use titles as links to other pages because the tab titles are already links. Beyond this, it sounds a bit off from a design perspective, since clicking on a tab is supposed to open that tab, not a new page. A hyperlink title is counter to user expectations, breaking the Principle of Least Astonishment. Perhaps you could place the link in its own fixed box in a viewport corner? This would also serve to highlight the link, setting it apart from the tabs and drawing attention to it (assuming that’s desirable).

That’s all I’ve got for you.

Though the generated HTML for the share buttons includes <?php the_permalink() ?>, it isn’t evaluated. Instead, the ShareThis plug-in replaces it (using preg_replace()) with the results of get_permalink(). This means you can’t replace the <?php the_permalink() ?> in the HTML, and hooking the the_permalink filter won’t do any good.

Original post as follows:

<div style=”text-decoration: line-through;”>
ShareThis’ WP plug-in uses the_permalink() for the URLs. It doesn’t add the query parameters from the current page by default (as it could cause problems with some sites), but you can create a the_permalink filter to add the query parameters used to request the current page to the permalink URL (the_permalink filter page includes an example on how to append the query string). Note that this will add the query parameters to ALL permalinks, which may cause other issues. If you’re not a developer, you may need to get one to help you.

Another option (one that will only affect the URLs used in ShareThis links) is to edit the HTML tags from within the ShareThis settings page. Replace all occurances of <?php the_permalink(); ?> with <?php echo add_query_arg($_GET, get_permalink()); ?>.
</div>