mazoola

Chester –

No, that’s a great help. I was looking at this a couple of days ago until I began to go cross-eyed, but I’m almost ready to jump back in.

One thing I found that looked potentially useful was this — especially the section on flushing rewrite rules on activation.

At one point he describes the 4-step process that occurs whenever a plugin is activated — which I assume also occurs when Divi returns from upgrading itself.

1. The browser loads the plugins.php file.
2. plugins.php file includes admin.php file. As a result, all other plugins have been loaded, and the init hook has already been called. WordPress doesn’t even know our plugin is activated yet, so of course your register_post_type() function hasn’t been hooked into init. Consequently, your CPTs are not registered.
3. Then plugins.php calls activate_plugin()
4. Our plugin is included, and your activate() function is called. Rewrite rules are flushed, but because your CPTs are not registered, nothing really changed.

This chain of events might sound simple and straightforward to you, but it got me every single time I create a plugin. Every. Single. Time.

I don’t know if that parallels Airpress’s experience, but I thought it might be worth a look.

(FWIW, I’m upgrading from the console. This doesn’t seem to be a common problem with Divi, as the only post on Elegant Themes’ Divi board concerning 404s after upgrade is from 2014 and was caused by a WordPress bug involving child themes.)

I’ve had two teapot-sized tempests blow up in the last couple of hours that, irritatingly, have to be calmed. If I free myself from them quickly enough, maybe I’ll kick things around a bit more.

Thanks again!

• This reply was modified 6 years, 7 months ago by mazoola.

Another Divi update — and more 404s. After the update, the rewrite rules inspector plugin showed all Airpress rewrite rules as missing. When I checked the Airpress Virtual Post definitions, though, they showed there were matching records for the test URLs. I noticed one VP didn’t show matches, so I changed the regex from (*.) to ([^/]+)/?$ and saved the VP. At that point, the rewrite plugin showed all rules present, and my Airpress-powered pages began appearing again. I assume the call to flush_rules() was responsible for the fix, but I’m not conversant enough with WordPress programming to understand why it’s not being called (or, if it is being called, what might be blocking it) on the return from maintenance mode.

Hope this helps…

Edit:
In looking through 1.1.42, I don’t see any calls to flush_rules outside of the *Admin modules. Should there be a flush call hooked to plugin activation or loading as well?

• This reply was modified 6 years, 7 months ago by mazoola.

Oops.

No, all three VPs have valid sort fields…

I’m in and out today, but I’ll text you when things settle down and we can figure out next steps. (I wish I could find a reliable trigger — or at least a way to make sure one of my deactivated plugins wasn’t the cause, as I don’t want you jumping through hoops needlessly.)

I’m pretty sure all three VPs are using the regex you suggested a while back.

Yep:
^wardrobe/garment/([^/]+)/?$
^wardrobe/outfit/([^/]+)/?$
^wardrobe/item/([^/]+)/?$

Thanks for the pointer to the plugin; I’ve been driving myself mad writing comment statement after comment statement. I had been wondering if you or anyone else made use of IDEs and, if so, which one, but this might be everything I need.

Chester –

After far too much banging of my head against the wall, I hit upon the boneheadedly simple idea of extracting the first image’s URL and storing it as an Airtable field. Unfortunately, I don’t seem to be able to access either thumbnail URL through Airtable, so very large images can slow down initial page loads — but I can now get back to the business of actually building the app.

I’d still like to understand better the combined Airpress/WprdPress loop, as the one thing I managed to learn after hours of tracing through the code was I’d been looking in entirely the wrong place: The shortcodes referencing the images were being stripped or [incorrectly] replaced well before my window of visibility opened.

Unfortunately, I’m also nearing the end of what I can accomplish using only shortcodes — and, so far, my experience with using both shortcodes and PHP routines on the same resource hasn’t been the best. The next couple of weeks, I’ll be moving within the city, but once that’s done expect me to pipe up even more frequently with questions