Title: webmaster808's Replies | WordPress.org

---

# webmaster808

  [  ](https://wordpress.org/support/users/webmaster808/)

 *   [Profile](https://wordpress.org/support/users/webmaster808/)
 *   [Topics Started](https://wordpress.org/support/users/webmaster808/topics/)
 *   [Replies Created](https://wordpress.org/support/users/webmaster808/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/webmaster808/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/webmaster808/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/webmaster808/engagements/)
 *   [Favorites](https://wordpress.org/support/users/webmaster808/favorites/)

 Search replies:

## Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SendGrid] PHP7 Compatible?](https://wordpress.org/support/topic/php7-compatible-19/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/php7-compatible-19/#post-9039078)
 * The plugin works fine on PHP 7.0 now. Haven’t tested with PHP 7.1 but those are
   warnings, not errors. They are deprecation notices and the functions they mention
   are deprecated in 7.1, and will be removed in 7.2. They are still there and the
   plugin should still function as designed. Unless you need to run PHP 7.2(which
   isn’t even going to be released until Dec. 2017 or later), it’s all good now.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Posts as post type archive](https://wordpress.org/support/topic/posts-as-post-type-archive/)
 *  Thread Starter [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/posts-as-post-type-archive/#post-8368277)
 * Yes, there are new posts published every day or two.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Making Dev Site On Nginx](https://wordpress.org/support/topic/making-dev-site-on-nginx/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/making-dev-site-on-nginx/#post-8359829)
 * Glad you got it working, there is often more than one way to skin a cat, but 
   normally it is not necessary to do what you are saying works for you. None of
   my configs are set up like yours and I don’t have any `RELOCATE` definitions 
   in wp-configs. Not saying that’s a problem, but it is interesting!
 * According to a tech I spoke to recently at Rackspace, specifying an IP in the`
   listen` directive was potentially useful in older versions of nginx, but is unnecessary
   in newer versions(I don’t need to do that on my sites). What version are you 
   running?
 * I’m also surprised that the ‘[http://&#8217](http://&#8217); string in your `
   server_name` directive isn’t throwing an error. The server name is not supposed
   to include the scheme, IIRC.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Making Dev Site On Nginx](https://wordpress.org/support/topic/making-dev-site-on-nginx/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/making-dev-site-on-nginx/#post-8355443)
 * You have not mentioned that you have created an additional nginx configuration
   file for the new host. nginx needs to have one configuration file for each host
   that you want to serve.
 * So you will need to clone the config file for example.com and change the `server_name`
   directive to example_dev.com and also set the `root` directive to the path to
   your _dev install directory.
 * After you have created the config file for the dev site, make sure to restart
   nginx.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Disable Embeds] Disable post slug change](https://wordpress.org/support/topic/disable-post-slug-change/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/disable-post-slug-change/#post-7815003)
 * [@j2trumpet](https://wordpress.org/support/users/j2trumpet/),
 * AFAIK, you will not be able to get a page that has the URL “[http://example.com/embed&#8221](http://example.com/embed&#8221);
   because “embed” is a [Reserved Term](https://codex.wordpress.org/Reserved_Terms).
 * In this case, the term “embed” already exists because it has been created by 
   WP Core so when you try to create a Page with the slug “embed” the slug sanitizer
   sees that there is already a term with that string and it appends the “-2” to
   make sure that the resulting permalink is unique. It will do this with any non-
   unique slug, not just reserved terms.
 * Perhaps you might consider a page called “embeds”? You could also perhaps create
   Page called “emb” and then a child of that called “ed”. Then you could have an
   URL like “[http://example.com/emb/ed&#8221](http://example.com/emb/ed&#8221);
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Custom Post Type Permalinks] Latest update Giving Errors](https://wordpress.org/support/topic/latest-update-giving-errors/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/latest-update-giving-errors/#post-7243040)
 * There is a single white space before the opening <?php tag in that file. If you
   edit the file and delete the white space, the error will go away.
 * Hopefully the author will fix this in the next version.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Rackspace CDN] Uninstalling the plugin restores the orignal link?](https://wordpress.org/support/topic/uninstalling-the-plugin-restores-the-orignal-link/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/uninstalling-the-plugin-restores-the-orignal-link/#post-5838321)
 * dhaval.gloob,
 * If you inserted images into posts after you installed this plugin, then the CDN
   URL is “baked” into the post content in your database. Things that are dynamically
   built(like featured images) should revert to the local URL(based on attachment
   metadata) once you uninstall the plugin.
 * You may need to do a search/replace on your database to fix this. Here is a script
   that works very well. [https://interconnectit.com/products/search-and-replace-for-wordpress-databases/](https://interconnectit.com/products/search-and-replace-for-wordpress-databases/)**
   You must be VERY CAREFUL with this script, you can destroy your database very
   easily**.
 * Basically, you only want to search the wp_posts table and make sure you only 
   search the post_content column.
 * You could set up a filter to replace/fix URLs in the content as well, or perhaps
   a simple jQuery snippet will do?
 * Tom
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Rackspace CDN] Post attachment guid is still local path](https://wordpress.org/support/topic/post-attachment-guid-is-still-local-path/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/post-attachment-guid-is-still-local-path/#post-5651535)
 * jameskzhao,
 * It appears that you are assuming the GUID is a path or URL, it is not.
 * While the GUID looks strikingly similar to a URL, it is not a URL but a Globally
   Unique Identifier. A unique string that is never supposed to change once it is
   created, even if your domain name and URL structure change. Instead of generating
   random alphanumeric GUIDs such as in a noSQL database, the WordPress core creates
   a string that looks like a URL, but is not.
 * The correct way to “refer to the path of this attachment” would be to use either`
   wp_get_attachment_url($id);` or `wp_get_attachment_image_src( $attachment_id,
   $size, $icon );` Those functions will(should) return the proper URL of the media
   resource on the CDN.
 * Tom
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [How can you create anchor links in menu drop down?](https://wordpress.org/support/topic/how-can-you-create-anchor-links-in-menu-drop-down/)
 *  [webmaster808](https://wordpress.org/support/users/webmaster808/)
 * (@webmaster808)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/how-can-you-create-anchor-links-in-menu-drop-down/#post-4740996)
 * Five easy steps to get what you want
 * 1. Get this plugin. [https://wordpress.org/plugins/custom-menu-shortcode/](https://wordpress.org/plugins/custom-menu-shortcode/)
 * 2. Create a new custom menu in Appearance>Menus. Let’s call it Menu Menu.
 * 3. Create your menu items by using the “Links” menu object type.
 * In the config box for the first Link Menu Item, you would use something like 
   this assuming you have a top level page named Menu:
 * URL: [http://yoursite.com/menu/#section_one](http://yoursite.com/menu/#section_one)
   
   Link Text: Section One
 * The next one would be:
 * URL: [http://yoursite.com/menu/#section_two](http://yoursite.com/menu/#section_two)
   
   Link Text: Section Two
 * 4. Then in your “Menu” page use the wordpress custom menu shortcode to insert
   the menu into the page like this:
 * `[custommenu menu="Menu Menu"]`
 * Now you should see the Section One and Section Two menu items within the “Menu”
   page content. You will probably need to adjust your css to get them to display
   how you want(as a dropdown) but the links should be there.
 * 5. Then all you have to do is add `id="section_one"` and `id="section_two"` to
   the elements where you want to jump to
 * Another way would be to use a form select element with a click handler script
   that would redirect to the page anchor.

Viewing 9 replies - 1 through 9 (of 9 total)