aspsa

Cory, thank you for the follow-up post and, as I may have mentioned in other posts elsewhere, I appreciate your developing this plugin for the WordPress community. I revisited the virtual machine version of Local by Flywheel, known as “Local Classic”. The newest non-VM version is called “Local Lightning”, and Local by Flywheel no longer supports Local Classic.

After completing the entire Duplicator Lite migration process (see this thread for the steps I took) from my original WP site as hosted in Local Classic to a newly created WP site also hosted in Local Classic, I can report that it performed seamlessly. First, I did not receive the “Sorry, you are not allowed to access this page.” error message. Second, when Duplicator Lite prompted me to log in as administrator, I was able to do so and, as had occurred at all times previously when I ran this process within the Local Classic application, Duplicator Lite automatically deleted the installer files.

This experience is bittersweet. It works but only within Local Classic and not within Local Lightning, again, where the former is no longer supported by Local by Flywheel. I cannot conclude that Local Lightning somehow does not support the Duplicator Lite plugin, especially since plugin integration occurs at the WordPress framework level and should be independent of the web hosting environment. As previously mentioned, perhaps Local Lightning requires configuration file tweaking. However, I do not feel confident that pursuing this path will resolve this problem nor do I believe it is a trivial ‘fix’, which leads me to ask the following question:

Can you kindly provide a list of local development platforms and versions under which Duplicator Lite has been tested? Let’s assume we are using WordPress version 5.6.2. Here are some platforms that come to mind:

Local by Flywheel (Class & Lightning)
XAMPP
WAMP
Laragon
Laravel Valet (Mac OS only)

[UPDATE]

In the interim, I tried a different approach by bypassing the Duplicator Lite WP plugin altogether and, instead, relying upon Local Lightning’s WP web site export capability. Here are the steps I took:

1. Deleted the migrated version of the original WP web site
2. Dragged & dropped an exported zip file of the original WP web site into Local Lightning. The exported version was imported into a new location and name of my choosing. However, during the provisioning process, a warning message appeared stating the import process failed to import several SQL files.
3. After excepting the warning message, I allowed the import process to conclude.
4. I compared the SQL files in question between the original and newly imported versions of the WP web site. However, contrary the warning message, I confirmed that the SQL files in question actually did import into the WP web site and their file sizes were identical.
5. I opened the newly imported WP web site and everything seemed to be in order

I’ll have to examine the newly imported WP web site over time to see if there are any anomalies. However, at first sight, it appears the Local Lightning import & export processes work well enough and that this my be my process of choice when working on multiple versions of a WP web site within the Local Lightning development environment. Still, I need to resolve the Duplicator Lite issues mentioned in this thread, because I require this process to work when moving my WP web sites between development and production environments.

I resolved the issue by changing

<?php
$product_image_01 = get_field("product_image_01");
?>
<img src="<?php $product_image_01; ?>" />

…to…

<?php
$product_image_01 = get_field("group_product_image_01");
?>
<img src="<?php $product_image_01; ?>" />

I discovered this by revealing the custom post’s metadata as follows:

<pre><?php print_r(get_post_custom($product_owner_link); ?></pre>

The PHP $product_owner_link variable references an Advanced Custom Field (ACF) relational field which points to the custom post in question having the product image that I want to display. For usability purposes, I leveraged ACF’s group and tab features. In the way that I nested the product image custom field, ACF prepended “group_” to the existing “product_image_01” custom field’s field name.

Steve, I appreciate the reply and will repost to the link you provided. Not sure if I am able to delete this post, as I do not want to cross-post if possible.

Thank you.

Thank you for the reply, Liew.

>> Are you able to stream your video file on the NAS from your web browser?
>> If can’t then WordPress cannot get the video file for streaming too.
Yes. In my web browser, I log into my NAS, and the NAS File Browser app opens by default. The URL address line displays the following:

<my IP address>/#app_board-com_seagate_filebrowser

Interestingly, when I drill down the directory structure to a specific video file, the URL address remains the same. After selecting the video file, the NAS File Browser app opens a media player from within which I can stream the content. Note, the media player runs within the NAS File Browser context and not as a standalone media player. This differs from accessing the very same file over my LAN using Windows File Explorer. In this case the default media player instantiates and loads the video. However, when playing the content, it is streamed from the NAS in both cases (i.e., via the web browser; via the instantiated media player).

The obvious challenge here is determining the specific URL, as the NAS File Browser application abstracts the publicly displayed URL in the manner shown earlier, and the URL address remains the same for any path location of a given video file.

Any thoughts?

• This reply was modified 5 years, 6 months ago by aspsa.

Never mind. When adding a ‘Video’ player, for example as a video block in Gutenberg, the ‘Upload’ button actually achieves what I need. I was not thinking of ‘upload’ from the site’s perspective.

Leiw, thank you for the reply. The WP 5.3 change explains the auto-generated “scaled” image. With respect to the additional auto-generated images, I created a WP theme from scratch and, for testing purposes, commented out all custom-sized image code in my functions.php file. The only auto-generated images in my theme should only relate to those defined in WP’s media settings and the WP 5.3+ auto-generated scaled image.

Any thoughts as to why the additional images I noted in this thread are auto-generated by WP? Thank you.