Title: Abacomancer's Replies | WordPress.org

---

# Abacomancer

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Adding New Plugin Behavior](https://wordpress.org/support/topic/adding-new-plugin-behavior/)
 *  Thread Starter [Abacomancer](https://wordpress.org/support/users/abacomancer/)
 * (@abacomancer)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/adding-new-plugin-behavior/#post-6692378)
 * **Somesh79**: I wasn’t looking for a workaround so much as an explanation if 
   one could be found. Like I said earlier, I have done successful manual plugin
   installs already. I’m confident the owner and group is set correctly. WordPress
   can edit plugin files via backend, and it can upload to the uploads folder with
   the same permissions. Even if they weren’t correct, setting everything to world
   writable would have bypassed that, as I understand it.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Adding New Plugin Behavior](https://wordpress.org/support/topic/adding-new-plugin-behavior/)
 *  Thread Starter [Abacomancer](https://wordpress.org/support/users/abacomancer/)
 * (@abacomancer)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/adding-new-plugin-behavior/#post-6692321)
 * **Somesh79**: No errors come up with debug, it still just redirects to the ftp
   login credentials request page.
    **catacaustic**: I thought the same, but on 
   the other hand, my 777 permissions test should have “fixed” that problem.
 * So I am thinking that this might be a problem with the uploading directory being
   different from the directory it is looking for the upload. Unfortunately, I’m
   not sure how to further fix/test for this.
    I’m making that guess based on the
   following:
    - 777 permissions did not fix this
    - I can edit plugin files (and save the changes) through the WP backend.- so
      wordpress/the server has write permissions
    - The zip files are still showing up in the media gallery + uploads directory.–
      this just seems like it shouldn’t be happneing
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Slideshow Gallery LITE] Loading js after gallery appears](https://wordpress.org/support/topic/loading-js-after-gallery-appears/)
 *  Thread Starter [Abacomancer](https://wordpress.org/support/users/abacomancer/)
 * (@abacomancer)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/loading-js-after-gallery-appears/#post-5565295)
 * Thanks for the help. I tried the method you gave, and it mostly works.
 * I had to remove the line $slideshow -> wp_head();
    I assume this is because it
   contains files not allowed in the body. Unfortunately, since the portfolio items
   are inside of an existing page, I cannot give them their own head. To add this
   file, I would have to somehow trigger this call in the head when a portfolio 
   item opens.
 * However, most everything for the gallery works appropriately as is (or can be
   fixed via styling), so I do not believe I will have to pursue that. The one problem
   I was having as a result of this is with ‘.slideshow-slider’. The CSS as-is without
   the header files forces it to width 22px with a high specificity and !important.
   Instead of fighting it, I just went into the files and removed the !important.
 * If you have a better solution, I would be glad to hear it. Either way, I am very
   happy I could get this working. Thank you again for your help.

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