Chester McLaughlin

Do you have a valid test URL for your VirtualPost configuration?

Do you have any special characters or accent marks (like é) in your VirtualPost configurations anywhere?

Also, what is your permalink setting?
/wp-admin/options-permalink.php

Strange. If you want to schedule some time for a screenshare for us to try and dig deeper you can do so at chetmac.com/contact/

In the meantime, you could try renaming your pages/paths (in case there is a weird conflict somewhere). So instead of

^repertoire/?$
^landing/([^/]+)/?$

you could try
^newrepertoire/?$
^newlanding/([^/]+)/?$

Are you running any caching plugins? If so, have you tried disabling it to see if that helps?

My guess is that you may have a VirtualPost configured that has a “bad” URL Pattern. The error (line 223) is smack dab in the middle of where WordPress is parsing the request (which relies on rewrites that Airpress and other plugins register).

If you want to copy/paste the URL Patterns for your various VirtualPosts into this thread, I’ll take a look.

Currently I’m only providing custom support/consulting if you reserve some of my time at calendly.com/chetmac

Be wary of “greedy” regular expressions.

Airpress (for better or worse) is a very low-level plugin. By which I mean that it hooks into WordPress’ core URL rewrite capabilities.

I frequently use Monkeyman Rewrite Analyzer plugin to see what is going on with ALL the plugins, custom post types, and pages that I have in a given WordPress install.

A greed regular expression would be something like “^/.*$” because it will match EVERY single URL that exists.

I worked through the issue with Justin and it turned out to be 1) a bad App ID and 2) a greedy regular expression.

Feel free to post your Virtual Post regular expressions here and I’ll let you know a few sample URLs they might match.

Thanks for the feedback. Hopefully we can get to the bottom of everyone’s issues. For what it’s worth, I haven’t found any “bugs” in the fundamentals of Airpress. It always turns out to be a conflict with a page builder, URL structure, or just a misconfiguration. That said, the plugin has a LOT of room for improvement when it comes to the configuration UI.

Yes. Let’s talk. Find me on the codementor website @chetmac
I would love to get more details on how you’d like the integration to work.

Yes. Let’s talk. Hit me up at https://www.codementor.io/@chetmac

I would love to get more details on how you’d like the integration to work.

https://gist.github.com/chetmac/42cf4aed5fc7bb161fc9092be3c63c4b

<?php
	$query->sort(
		[
			["field" => "My First Airtable Field", "direction" => "DESC"],
			["field" => "My Second Airtable Field", "direction" => "ASC"]
		]
	);

First off, what should happen if a user NOT logged in loads the page? Because we can’t “get_useredata” on a non-logged in user, and we don’t want to query Airtable for NULL or empty URLs.

Secondly, the purpose of a Virtual Post is to use a piece of the requested URL to fetch matching records from Airtable.

So some URLs like:
/airtable-users/chester
/airtable-users/matthew

Could use a single page (as a template) and a single Airpress Virtual Post configuration and load custom Airtable data into the template based on the requested URL.

If you want to fetch data based on the current logged in user, I would recommend just creating a normal WordPress page and then using a function in your functions.php file to either A) fetch the appropriate data and/or B) generate a custom shortcode to output exactly what you want where you want it.

Depending on your use case you could also have that function redirect users who are not logged in or just show a message telling them to login.

If you book some time with me at https://chetmac.setmore.com/ I can provide some code samples and probably provide a working solution in ~30 minutes.

Not currently with VirtualFields. You can with VirtualPosts.

Also you can with a custom function in your functions.php file.

Wordpress Field should be a property of the WordPress $post object.

So ID or post_name or post_title

Here’s the link to my quick Emoji support video:

Long story short—simply copy paste from Airtable into Airpress configuration/shortcodes and all should work as expected.

Surely. I’m testing out the emoji stuff now. So far it seems to work fine to simply copy paste emojis from Airtable into Airpress config, however I’m testing a little bit deeper as well. I’ll get back to you before noon today.

And if you’re on a mac and you’re dealing with Airtable, Airpress, and Emojis you can simply press “control command space” to bring up the character viewer.

https://support.apple.com/en-us/HT201586