Project

General

Profile

Actions

Support #15169

closed

new Prelude website zipfiles for custom theme and other files.

Added by Marilyn Weber over 2 years ago. Updated over 1 year ago.

Status:
Abandoned
Priority name:
Normal
Assignee:
-
Category name:
-
Target version:
Start date:
2022-01-08
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

The Segal theater people are now in touch about their new Prelude website at https://preludenyc2020.commons.gc.cuny.edu. They "have uploaded the zip file of the theme and its files here: https://drive.google.com/drive/folders/1KiUJ9Lt-Ols_Ht0dm-5ib-9_VHD85EkV?usp=sharing"

Is this all you need Boone? Happy to ask them for more - thank you!


Files

prelude20.zip (4.61 MB) prelude20.zip Boone Gorges, 2022-01-18 03:59 PM
Actions #1

Updated by Boone Gorges over 2 years ago

  • Status changed from New to Reporter Feedback

Hi Marilyn - Thanks for passing this along.

This package includes a list of plugins they want to use, but we don't have all of these plugins on the Commons:

1. CoBlocks
2. Crowdsignal Forms
3. Layout Grid
4. Page Optimize
5. wordpress.com Editing Toolkit

In a number of cases, I have misgivings about installing on the Commons.

1. We already have a number of block library plugins on the Commons: https://wordpress.org/plugins/kadence-blocks/, https://wordpress.org/plugins/atomic-blocks/.
2. We already have a number of form creation plugins on the Commons, including Gravity Forms and Ninja Forms
4. We generally do not offer performance plugins like this on the Commons, as they may not be compatible with our hosting infrastructure
5. The description for this plugin suggests that it's guaranteed to work only on wordpress.com, and that it's not really a production-ready plugin. https://wordpress.org/plugins/coblocks/

In general, we ask partners to try to use plugins that we already have on the site. And when they can't, we prefer that they reach out to us regarding potential plugins before designing their site around them, in case of incompatibility. See https://dev.commons.gc.cuny.edu/hosting-partner-handbook/ for more. It's possible that some of these plugins (at least 1-3) could be made available on the Commons, but there'd have to be overwhelming reason for providing duplicate functionality.

If the Prelude team needs these specific plugins, it may be best to seek more flexible hosting. If they'd like to host on the Commons as in the past, it may be best to consider plugins that we've already got on the site.

Actions #2

Updated by Marilyn Weber over 2 years ago

Thanks, Boone, I've passed this along.

Actions #3

Updated by Marilyn Weber over 2 years ago

I don't see the custom theme as an option. Is it uploaded? He replied "The response from your lead developer is appreciated and I can go forward by using the alternative plugins suggested.

If you could upload the custom theme file that I shared to the site, that would be great and I can go ahead with the plugins work through."

Actions #4

Updated by Boone Gorges over 2 years ago

I haven't yet added the theme because there was a possibility that my answer would cause the team to find a new host.

I've done an initial review of the theme, and it's left me a bit confused about what to do with it. It's filled with hardcoded references to preludenyc2020.com. But it's 2022. What will the final URL of the site be? Generally, WP themes try to avoid using the hardcoded url (use home_url() instead). Also, what Commons site should the theme be made available on? Will there be a new site for this year's event, in the same way that there has been in past years?

Actions #5

Updated by Raymond Hoh over 2 years ago

Boone, it looks like they are staging their site on preludenyc2020.com, which is a wordpress.com site. That would explain the XML containing the domain. This also explains some of the posts in #15170. Probably due to an import.

Actions #6

Updated by Marilyn Weber over 2 years ago

Reply from Guarav:

"Hi Marilyn, thanks for sharing this response. I'm responding below:

  • The final URL of this site will be https://preludenyc2020.commons.gc.cuny.edu/
  • It would be great if you could replace any references to preludenyc2020.com to home_url(). After the theme is up and running, I can go into the theme files and replace any additional hardcoded URLs with the updated domain name.
  • The commons site for the theme to be made available on is https://preludenyc2020.commons.gc.cuny.edu/
  • For Prelude 2022, a new site will be built on the Commons itself. We've witnessed the challenges that comes up building a site outside the Commons framework for 2020 and 2021 and then porting it to this framework.

Please let me know if the developer has any additional questions. I'm happy to be put in touch with them directly to coordinate."

Actions #7

Updated by Boone Gorges over 2 years ago

Thanks, Marilyn. Please pass the following along to Guarav:

In general, our team doesn't have the resources to make changes to your theme on your behalf, but as a courtesy I've done some of the hardcoded URL swapouts. See the attached prelude20.zip.

In making these changes, I've noticed some references to URLs like .../wp-content/uploads/2020/... It's almost certain that these URLs will not work, in part because the WP importer will not guarantee the same folder structure (2020 vs 2022) and in part because the Commons multisite installation uses a different way of mapping the upload directory URL for its sites. I'd recommend moving these image and video assets into a theme directory, and then embedding like this:

<img data-toggle="modal" data-target="#globe" width="100px" height="100px" style="cursor:help" src="<?php echo esc_url( get_stylesheet_directory_uri() ); ?>/img/clippy-help.gif">

Once you've made these modifications, please pass an updated zip back to me, and I'll slot this theme for the next release (Tuesday Jan 25).

Actions #8

Updated by Matt Gold over 2 years ago

Thank you so much for the extra time you put into this, Boone.

Actions #9

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.2 to 1.19.3
Actions #10

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.3 to 1.19.4
Actions #11

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.4 to 1.19.5
Actions #12

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.5 to 1.19.6
Actions #13

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.6 to 1.19.7
Actions #14

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.19.7 to 1.19.8
Actions #15

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 1.19.8 to 1.19.9
Actions #16

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 1.19.9 to 1.19.10
Actions #17

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 1.19.10 to 2.0.1
Actions #18

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 2.0.1 to 2.0.2
Actions #19

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 2.0.2 to 2.0.3
Actions #20

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 2.0.3 to 2.0.4
Actions #21

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.0.4 to 2.0.5
Actions #22

Updated by Boone Gorges over 1 year ago

  • Target version changed from 2.0.5 to 2.0.6
Actions #23

Updated by Marilyn Weber over 1 year ago

I think you can mark this as abandoned now. Haven't heard from them in a long time.

Actions #24

Updated by Boone Gorges over 1 year ago

  • Status changed from Reporter Feedback to Abandoned

Sounds good, thanks!

Actions

Also available in: Atom PDF