jonathanlb/signed-s3-links

Update shortcodes to render with Divi Builder

Open

#9 opened on Mar 9, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PHP (0 forks)auto 404
bugenhancementhelp wanted

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

When a WordPress post contains more than 12-18 ss3 shortcodes, Divi Builder will not display previews for many ss3 shortcode invocations, instead showing a spinner and logging a 504. Editing the DIVI module content seems to trigger rendering and removes the spinner, suggesting to me that Divi Builder running at my host is overwhelmed with requests.

The post renders cleanly to the client, however.

I ran across the 504s performing mass replacement (site names redacted):

time wp search-replace '\[et_pb_audio audio="https://XXX/wp-content/uploads/([a-zA-Z0-9_\-]*.mp3)" title="([^"]*)" artist_name="([^"]*)".*?(?=\[/et_pb_audio\])\[/et_pb_audio\]' \
'[et_pb_code][ss3_audio XXX/\1 style="width: 100%;" region=us-east-2 class="wp-audio-shortcode" title="\2 by \3"][/et_pb_code]' \
wp_XXX_posts --include-columns=post_content --regex

Is there some way to update the shortcodes to be more friendly with Divi Builder preview?

Contributor guide

Research direction
Inspect the plugin's shortcode callback and the way it renders output. Research how Divi Builder loads previews and what causes the 504 timeout when many shortcodes are present. Look for methods to optimize or bypass rendering in preview contexts, such as checking for Divi's AJAX requests or using caching.
Tech stack
php
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPHPWordPress
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45