Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WP: curriculum site wordpress problems #2438

Open
stenington opened this issue Mar 23, 2020 · 8 comments
Open

WP: curriculum site wordpress problems #2438

stenington opened this issue Mar 23, 2020 · 8 comments

Comments

@stenington
Copy link
Contributor

stenington commented Mar 23, 2020

The curriculum Wordpress site has a few ongoing issues. Some pages break regularly after deployments from staging, and there seem to be translation problems happening as well.

Iridescent-CM/technovation-wp#94
Iridescent-CM/technovation-wp#93

We're trying to collect additional information on the problems and coping mechanisms.

@hellafitz
Copy link
Collaborator

@rsgonzal to follow up

Questions for Maggie (for each ticket, if possible)

  • What patterns she’s seeing?
  • How much time it takes to correct the error(s)
  • What has to be done to do the fix
  • If the fixes are permanent (at least until the next deployment)
  • [bonus/stretch: document the process she's using]

@rsgonzal
Copy link
Collaborator

@rsgonzal
Copy link
Collaborator

rsgonzal commented Mar 24, 2020

Blank pages are more common that the broken styles
Translation drop-down on curriculum pages breaks

What patterns she’s seeing?

How much time it takes to correct the error(s)

  • if she knows what pages are broken, it's doesn't take very long
  • maybe a minute or two per page
  • gets confusing when she doesn't know which pages are broken, the circle tool helps with that but it still doesn't tell her which translation boxes are broken.
    ^^this takes longer to do, when she sees pages consistently breaking she adds them to spreadsheet to check them. Takes ~20 mins once or twice a week

What has to be done to do the fix
Fixes are permanent until the next deployment

  • open Beaver Builder on production and just saving - this is quick fix
  • open broken page on staging using Beaver builder, make a very small edit, save change and publish and push live - better practice and page doesn't break again, but other pages still break

@rsgonzal
Copy link
Collaborator

Has also tried clearing the Beaver Builder cache before pushing live (as well as after) and it didn't make a difference. Broken pages were still broken.

@hellafitz
Copy link
Collaborator

@rsgonzal to check in with Maggie and get a status update

@rsgonzal
Copy link
Collaborator

from maggie:

They have not broken in many many weeks (since April 9 or so). We also have not made that many updates to them recently so I don't know that the glitch itself is solved for good, but it's been pretty smooth, even for the non-curriculum pages that were also occasionally breaking.
I imagine the problem might re-emerge in the late summer/fall as we make more extensive edits to the curriculum, but for now things are good.

@rsgonzal
Copy link
Collaborator

rsgonzal commented May 20, 2020

There is a different glitch now:

  • italics styling seems to be broken across the site (on both production and staging). If text is in italics or set to italics, it defaults to Times New Roman italics. If it's changed to "default" styling, it reverts back to poppins.
  • my "fix" has just been to remove the italics styling when I come across it.
  • It doesn't seem to matter whether it was set in the text editor using the format buttons or in the module settings themselves.

Screen Shot 2020-05-14 at 5 49 22 PM

Screen Shot 2020-05-14 at 6 05 22 PM

  • Another error that would be super strange if was related is the little icon modules seem to default to italics (and I don't know how to fix that) -- you can see one example in the sidebar on the judge page: https://www.technovationchallenge.org/judge
    Screen Shot 2020-05-20 at 8 47 06 AM

@hellafitz
Copy link
Collaborator

@rsgonzal do you know if these issues have been resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants