Upload files to WordPress for GPS to stream events

Through a series of emails we have been asked to upload files to the WordPress directory to give a 3rd party read / write access through the theme editor. This will allow them to make changes to the file. Note: This does pose a security risk for us as that directory is locked down to prevent hacking.

Here is one of the emails.

James Gilmore <jgilmore@deweydigital.com>
3:20 PM (19 hours ago)

to Robert, Dominique, me, Tim
We have been able to test everything we needed to on the dev server.

However, several of our plans for implementation rely on the assumption that we will be able to edit the template through WordPress's theme editor, because there are several key points in the livestream schedule where items that are hardcoded into the template itself need to be tweaked in order to incorporate program changes. (That isn't an ideal situation, obviously, but it was a strategic choice we made based on the limited timeframe for development.)

At least for the template file (nea_ra_stream_template.php), we need to be able to change the file contents somehow for the following implementation points:

1. The template references specific post IDs in WordPress and a specific base directory for the images as PHP variables. Currently, they are referencing post IDs on the dev server, and a base directory on a Dewey-managed dev server, which we had been using to temporarily serve up the images while we've been getting everything through the approval process. We need to change those to their final post IDs and image base directory once we have those posts set up on the production site.

2. The ustream iframe—which is hardcoded into the template—is still currently referencing our test ustream channel, because NEA's ustream channel is not yet configured. Even the NEA ustream channel is likely not to be the final embed code, since Lyons will be building an email form overlay to go over the ustream code once we have embed code for the NEA ustream channel. That's all being handled between us and Lyons—but because that iframe code is hardcoded into the template, we need to be able to edit the template in order to make changes to that code.

3. The CoverItLive iframe—which is also hardcoded into the template—will only be active for the first day of the livestream, after which we will need to be able to remove or comment out that iframe code. Since that iframe code is hardcoded into the template, we need to be able to edit the template in order to make changes to that code.

4. Prior to the launch of the livestream itself next week, we are going to be using that same template for promotional "coming soon" text. This will require commenting out the ustream iframe and the CoverItLive iframe. Because those are both hardcoded into the template, we need to be able to edit the template in order to make changes to that.

5. Midway through the livestream schedule, starting July 3, we are going to need to switch out one image reference that is hardcoded into the template (visit_booth.png) to another image (visit_booth_2.png), to reflect a change in the location of the GPS Network booth at the RA.

Obviously, making that particular PHP file writable by WordPress isn't the only solution here; alternatively, we could prepare multiple versions of the template for you to upload and overwrite the existing template file at predetermined, specific times throughout next week, or if you're more comfortable giving us FTP access, we could upload new template files at those specific times ourselves without requiring your assistance. But our implementation plans require that the PHP template file itself be changed at several points throughout the process. Again, that's obviously not an optimal situation, but it's a result of the limited timeframe we've been working with.

I hope that clarifies things. Please feel free to touch base with me if you have any further questions, or any thoughts on how we might be able to address your concerns more effectively.

Thanks,

JGG