Local Community

Can't upload images to media library or add plugins when Live link is enabled

Bug Summary

Video Summary: Loom | Free Screen & Video Recording Software

Steps to reproduce

  1. enable, Live Link
  2. login
  3. attempt to add file to media library
  4. error

Environment Info

Describe your environment.

  • What Operating System are you using? Windows 10
  • What versions of site software (Nginx, Apache, PHP, MySQL) is used? Nginx
  • What version of Local is installed? 6.4.0+5927

Supporting info

Please provide your Local Log. See this Community Forum post for instructions on how to do so:

Include any screenshots or video recordings of the issue to help others reproduce.

Hello there! :wave:t3: Welcome to the Local Community.

Thank you for your video recording, it was helpful to see the steps you were walking through.

I am not able to reproduce that behavior on my end using the steps provided & a clean install, so I may need some more information.

In your video, I see that you are using the Oxygen builder. If that plugin is disabled are you able to upload media files?

I would recommend making a backup before trying that - you can do that following these steps:

:woman_technologist:t3: Sam

Hi Support!

I created a video outling me following your steps and still getting the error.

I also (during the video) created a whole new site and still got the error

Let me know our next steps!

Hey @keyinora, thanks for reaching out! That video is super helpful, I really appreciate it.

We’re able to reproduce too, so I have created a bug in our engineering backlog for the team to take a look. I’ll link that ticket to this forum post so that we come back here with updates.

I’m curious about your workflow, though (disclaimer, I’m the Product Manager on the Local team, I love getting to watch how users build with Local!). Do you typically build sites exclusively over that Live Link, or at least prefer that method? What do you like about building over that Live Link?

I’m curious how it compares to building the site over either a localhost (localhost:10000) or a site domain generated by Local (mysite.local). Obviously, these sites would only be local to your machine, so not viewable by others until that Live Link was turned on.

1 Like

Hi @austinwendt !

I have created a short loom video outlining how we use your service.

Let me know if I need to provide any additional information.

Hi Austin,

I discovered Local a few weeks ago and it solves the problem that my website is too big/complicated for my hosting provider. For what it’s worth, I have 8-9 custom post types with custom fields with about 20,000 posts, I use Custom Content Shortcode to pull content together across the content types, based on taxonomies and relationships.

I’m not using anything particularly special for the template though I’ve written a bunch of template files with embedded shortcode calls.

As an example, I have a page that displays >900 names of companies, pulling from a custom post type. Or another page that lists several hundred products. On my hosting provider, those pages can crap out. I was using WP-Rocket and Cloudflare to try to ameliorate the problem but it was still a problem.

Prior to Local, I was using Duplicator Pro to copy just my database to production. Unfortunately, my latest export (which was just under 10mb compressed) was a bit too much for the prod environment and I ended up with the white screen of death.

I imported my site to Local, installed Simply Static and exported the entire thing as static files (which works great for my use) and upload the resulting 23K files to prod.

As for Live Link: I moved my development machine to the basement. I use the Live Link url to work on it from my laptop anywhere in the house (or anywhere else). A friend asked about making blog posts on my site, so I gave him the link and now he can do that. Pretty fantastic in my opinion.

Last, I’m weighing in with a “me too” on the images. My friend and I discovered the problem this weekend. I went down a rabbit hole of MAMP/No-IP to try to find a way around it but did not (home router issues, mostly).