-
Notifications
You must be signed in to change notification settings - Fork 20
Expand file tree
/
Copy pathTODO
More file actions
96 lines (77 loc) · 4.18 KB
/
TODO
File metadata and controls
96 lines (77 loc) · 4.18 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
= 5.7.X =
* Disconnect/reconnect button when error on sitemap reported
* Clear log button
CONSIDER: log sitemap report fetch error and discconnect immediately? admin message?
= 5.8 =
* move sitemap reports to own tabs or one Reports tab for all sitemaps?
* add fetch sitemap data twice daily (or once an hour?) and store
* refetch after submit and store
* refresh buttons for sitemap data
* Quick edit field for Google News exclude
* Post list column for Google News exclude
* Reverse Disable sitemaps option in admin
= 5.9 =
* Sitemap index drilldown in reports
* rethink gsc onboarding: if multiple property candidates, manually choose between them before final redirect?
* RSS feeds: detect excerpt setting with admin warning or auto-change setting (?), suggest advanced plugin for improved compatibility
* lastmod for users
* include home page even if pages are excluded, but HOW ? back to root sitemap ???
* dummy dynamic slug field for google news advanced
* DROP theme template overrides
* revisit Polylang compatibility
* switch to Exclude post types
* Verify SEO framework compatibility (robots.txt, auto-deactivation seo fw sitemap...)
* change SEO compatibility warning messages (advise to use the seo plugin sitemap or upgrade to Advanced plugin?)
* revise SEO plugin compatibilty and conflict notices: maybe just recommend using SEO plugin sitemap, or completely ignore unless real conflict?
* optimize plugin index:
- can we prevent default queries? maybe do not update/prime meta caches etc?
- can we cache lastmod data as transients?
* Make leaner still: only load sitemap class and functions on xmlsf_sitemap_loaded ... same for news.
* Combine images: attached includes featured
* Make Polylang lastmod dates per language
* revisit get_lastmodified and/or _get_post_time: replace with core functions and some kind of caching maybe...
* revisit expensive meta_query for _xmlsf_exclude: maybe collect all posts with _xmlsf_exclude (and noindex?) occasionally and store their IDs for faster exclusion in db query... or or or better yet... store exclude IDs not as meta but in one DB option in the first place?
NEW
* remove post types that are not activated from admin tab
General settings for Home page:
* Consider: Option for lastmod date for (static) front and blog pages (PRO?):
- last publication date for post post type
- page modification date
++ advanced options
TEST
* Nginx Helper purge wildcard not working?
* test/fix outdated lastmod dates for post type sitemaps when Redis Cache is active
ROADMAP
* Unite settings under one admin page "XML Sitemaps"
* move sitemap fields (back) to Sitemap class?
* rethink xmlsf_post_types and optional xmlsf_post_type_settings
DOCUMENT
* Images in sitemaps, see https://wordpress.org/support/topic/how-to-include-featured-attached-images-in-xml-sitemap-not-one-or-the-other/
* xmlsf_blogpages
* xmlsf_frontpages
* xmlsf_register_news_sitemap_provider
* xmlsf_register_news_sitemap_provider_after
* xmlsf_add_settings
* xmlsf_news_add_settings
* xmlsf_clear_news_settings
* add inline comment blocks for hooks
CONSIDER
* Do we still need nginx fastcgi cache purge hooks with the new nocache headers?
* featured + attached images option
* Reset button per settings tab
* compatibility with https://wordpress.org/plugins/page-links-to/ ? option to automatically exclude linked posts... but not by default?
* make sitemaps_enabled use static value for faster repsonse
* Get rid of the whole feed business...
* Quick edit colums sortable
* Move update lastmod on comments to General section?
* make prime meta caches (async crawler?)
* drop all WP pre-5.5 and ClassicPress compatibility routines?
* core sitemap stylesheets per sitemap type (is that possible?)
* drop all publisher center links ? see https://support.google.com/news/publisher-center/answer/14859160
* Polylang news name option in translation strings? Or fix news name to blog name?
* move away from feed templates, adopt ?sitemap=... approach from core
* dynamic stylesheets
* revisit/regroup views
CORE SITEMAP:
* TODO Maybe add dedicated Media sitemap if image tags are (still) not possible OR completely replace the renderer?
* add custom post type root pages... with a separate "root" sitemap or in the main pages sitemap?