-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add original comments to .htaccess #65
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
Conversation
|
It would have been nice if you had described the compatibility problems you faced or quoted the part of the page that discusses the "BEGIN WordPress" and "END WordPress" comments (since I couldn't actually find anything on that page that does). As it was, I ended up looking around the source code to figure out what the issue might be. It looks like the relevant code is |
|
I haven't looked which functions use this comments, because it is the default behaviour of WordPress. I thought it is enough to reference to the WordPress codex. |
That's fine, but that page in the WordPress codex doesn't say anything about those comments being required. It may imply that by including the comments in all the examples, but as far as I could tell WordPress doesn't actually document the |
|
LGTM |
|
After changing permalinks setting, the content is set twice. Sure, this doesn't matter since it's the same content. But it doesn't look nice and future-compatible. And yes, WP use this comments only in this functions. I'm sorry, but I don't understand the need to discuss the motives of WP to use this comments. (btw, the oldest occurrence I could find is in version 2.3, and there's no reason WHY - misc.php. Let's say it's common law? 😉) |
|
Seems legit to me, especially given that the WordPress source reads these markers. 👍 |
|
(despite it not being properly documented, it is all over the codex and the forums as an accepted "thing" WordPress does) |
Add original comments to .htaccess
- `buildpack-deps`: `squeeze` (docker-library/buildpack-deps#21), `liblzma-dev` (docker-library/buildpack-deps#19) - `django`: 1.7.7 - `elasticsearch`: `java:7-jre` (docker-library/elasticsearch#4) - `java`: 8u40 (GA of OpenJDK 8!) - `logstash`: `logstash` user (docker-library/logstash#7) - `mariadb`: remove 10.1 (MariaDB/mariadb-docker#7) - `memcached`: LICENSE - `mongo`: 3.0.1 - `percona`: 5.5.42, 5.6.23 - `postgres`: correct perms on `/run/postgresql` (docker-library/postgres#52) - `rabbitmq`: 3.5.0 - `rails`: 4.2.1 - `sentry`: 7.4.1 - `wordpress`: add comments in `.htaccess` (docker-library/wordpress#65)
- `buildpack-deps`: `squeeze` (docker-library/buildpack-deps#21), `liblzma-dev` (docker-library/buildpack-deps#19) - `django`: 1.7.7 - `elasticsearch`: `java:7-jre` (docker-library/elasticsearch#4) - `java`: 8u40 (GA of OpenJDK 8!) - `logstash`: `logstash` user (docker-library/logstash#7) - `mariadb`: remove 10.1 (MariaDB/mariadb-docker#7) - `memcached`: LICENSE - `mongo`: 3.0.1 - `percona`: 5.5.42, 5.6.23 - `postgres`: correct perms on `/run/postgresql` (docker-library/postgres#52) - `rabbitmq`: 3.5.0 - `rails`: 4.2.1 - `sentry`: 7.4.1 - `wordpress`: add comments in `.htaccess` (docker-library/wordpress#65)
Ensure the compatibility by adding the original comments. See http://codex.wordpress.org/htaccess