Skip to content

Issues: WordPress/servehappy

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.

Sign up for GitHub

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

32 Open 7 Closed
32 Open 7 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Discuss recovery email filtering
#41 opened Mar 4, 2019 by schlessera 5.2
2
Modify README.md to provide more information on the servehappy initiative and link to all relative sources.
#35 opened Dec 18, 2017 by nerrad
@nerrad
Find replacements for incompatible plugins before upgrade section
#34 opened Oct 16, 2017 by felixarntz
3
Ask resident/contracted developer before upgrade section
#33 opened Oct 2, 2017 by schlessera
4
Ask hosting provider before upgrade section
#32 opened Oct 2, 2017 by schlessera
5
Ask plugin/theme support before upgrade section
#28 opened Oct 2, 2017 by schlessera
5
Updates before upgrade section
#27 opened Oct 2, 2017 by schlessera
3
Compatibility checker before upgrade section
#26 opened Oct 2, 2017 by schlessera
17
Backup & rollback plan before upgrade section
#25 opened Oct 2, 2017 by schlessera
6
Steps to ensure the website is ready for a PHP upgrade
#24 opened Aug 28, 2017 by felixarntz
3
PHP 7.0+ has 64-bit support to Windows environment audience: developer audience: site-owner benefit
#23 opened Aug 28, 2017 by Rahmon
Goal: help troubleshoot issues goal section
#22 opened Aug 26, 2017 by schlessera
Goal: give instructions on updating PHP goal section
#21 opened Aug 26, 2017 by schlessera
Goal: provide steps to prepare an update to PHP goal section
#20 opened Aug 26, 2017 by schlessera
Goal: list the potential problems an update might cause goal section
#19 opened Aug 26, 2017 by schlessera
Goal: explain why WordPress can’t deal with this problem itself goal section
#18 opened Aug 26, 2017 by schlessera
Goal: explain what an update is goal section
#17 opened Aug 26, 2017 by schlessera
Goal: explain the benefits of new PHP goal section
#16 opened Aug 26, 2017 by schlessera
Goal: explain what the problem with old PHP is goal section
#15 opened Aug 26, 2017 by schlessera
Goal: explain what PHP is goal section
#14 opened Aug 26, 2017 by schlessera
Introductory paragraph - "probability" approach section
#13 opened Aug 26, 2017 by schlessera
1
Introductory paragraph - "detected issue" approach section
#12 opened Aug 26, 2017 by schlessera
Introductory paragraph - "technology" approach section
#11 opened Aug 26, 2017 by schlessera
A modern version allows using the latest PHP features audience: developer audience: site-owner benefit
#9 opened Aug 17, 2017 by felixarntz
3
A modern version will keep WordPress alive audience: developer audience: hoster audience: site-owner benefit
#8 opened Aug 17, 2017 by felixarntz
2
ProTip! Add no:assignee to see everything that’s not assigned.