Title: toddulus's Replies | WordPress.org

---

# toddulus

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[Raft] Hamburger menu broken because of CORS error](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/)
 *  Thread Starter [toddulus](https://wordpress.org/support/users/toddulus/)
 * (@toddulus)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/#post-17855054)
 * [@ais100](https://wordpress.org/support/users/ais100/) Yep no worries. There 
   is probably a more elegant solution, but this worked for me for now. Also this
   is a GoDaddy error, so GoDaddy should fix it, but in the meantime…
 * Edit file top section of .htaccess file to include this header: 
   **Header set
   Access-Control-Allow-Origin “\*”**
 * e.g:
 * `# BEGIN GD-SSL
   <IfModule mod_rewrite.c>...Header add Strict-Transport-Security"
   max-age=300"Header always set Content-Security-Policy "upgrade-insecure-requests"**
   Header set Access-Control-Allow-Origin "\*"</IfModule># END GD-SSLFor the change
   to be applied, clear your site’s cache in the Go Daddy console.
 * Go carefully when editing this file. I suggest creating a backup of the file 
   before editing it.
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[Raft] Hamburger menu broken because of CORS error](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/)
 *  Thread Starter [toddulus](https://wordpress.org/support/users/toddulus/)
 * (@toddulus)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/#post-17853997)
 * Thanks [@rodicaelena](https://wordpress.org/support/users/rodicaelena/)
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [[Raft] Hamburger menu broken because of CORS error](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/)
 *  Thread Starter [toddulus](https://wordpress.org/support/users/toddulus/)
 * (@toddulus)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/hamburger-menu-broken-because-of-cors-error/#post-17853807)
 * I got it working. Had to change .htaccess. AS I suspected it was related to GoDaddy
   config – somehow. I have a working theory that this relates to GoDaddy config
   and the April upgrade to WordPress 6.5 
   Still can’t figure out why it wasn’t 
   a problem for other local javascript files.I should point out this issue occured
   on many themes, not just Raft

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