New to project nami - limited dashboard use

Hi, I'm trying to update an elegant theme and plugin to an existing website where the version is expired. Usually this would be done in the dashboard (nice and easy) but I'm unable to (runs on project nami). I'm hitting a lot of brick walls for simple tasks. Any help would be much appreciated. Thanks Emma

Hello anyone there?

[patrickebates]

Must have missed the first notification.

Exactly what is failing? And is this site hosted on Azure Web Apps or IIS? I ask because Web Apps has a max thread time of 3 minutes, and it can cause updates within WP to fail if they take longer than that, regardless if vanilla or PN. For example, I can't get Jetpack to update on most sites I manage on Web Apps and have to FTP the files up.

Thanks for responding. For me it's not being able to use the dashboard in a normal way. This is the error after an attempted theme update;
https://wwwdev-eb.tursa.com.au/
Warning: require_once(C:\inetpub\wp-eb-www/wp-content/themes/Divi/post_thumbnails_divi.php): failed to open stream: No such file or directory in C:\inetpub\wp-eb-www\wp-content\themes\Divi\functions.php on line 40

Fatal error: require_once(): Failed opening required 'C:\inetpub\wp-eb-www/wp-content/themes/Divi/post_thumbnails_divi.php' (include_path='.;C:\php\pear') in C:\inetpub\wp-eb-www\wp-content\themes\Divi\functions.php on line 40

Is there paid support we can request to help get it functioning normally? Or; is there support in the form of how to use PN. The WordPress community don't seem to know much about PN. If you can point me in the right direction that would be great thank you

[patrickebates]

PN is pretty much just vanilla WordPress, except that themes and plugins which attempt direct DB access using MySQL specific syntax have a chance of failure.

I'm not familiar with Divi, but the error you have makes me think the theme didn't unpack correctly from the dashboard. That shouldn't be a problem with PN itself. I recommend that you start with downloading the theme yourself and unpacking it into the theme folder manually. That may resolve the issue.

Ok will try that thanks Patrick