You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I noticed the plugin "Nggallery" is looking for a folder called "gallery" in wp-content inside the wordpress installation, rather than the site specific wp-content folder.
Is it correct accessing the admin panel through my-site.loc/wordpress/wp-admin ?
I'm new to wordpress development and might be missing something
The text was updated successfully, but these errors were encountered:
I haven't looked at the code for that plugin, but if it hard codes the content or plugins directory, it will have problems when WordPress is installed in a subdirectory within the site url.
The dashboard is accessed through /wordpress/wp-admin, though in some cases, it will forward you to the right place from /wp-admin.
Thanks for answering!
The plugin uses the constant ABSPATH defined in wordpress wp-load.php eg. /home/jn/www/lala/wp-sites/wordpress/ thus it will look the wrong place!
Do you know any way to work around this? For now I'm just symlinking the gallery folder
Use a different one (or the built in media galleries)
But I am surprised that nextgen gallery doesn't support wordpress in a
subdirectory, being a pretty popular plugin. Maybe there is something else
going on.
Thanks for answering!
The plugin uses the constant ABSPATH which is
/home/jn/www/lala/wp-sites/wordpress/ thus it will look the wrong place I
suppose!
Do you know any way to work around this?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-17924703
.
Hi, I noticed the plugin "Nggallery" is looking for a folder called "gallery" in wp-content inside the wordpress installation, rather than the site specific wp-content folder.
Is it correct accessing the admin panel through my-site.loc/wordpress/wp-admin ?
I'm new to wordpress development and might be missing something
The text was updated successfully, but these errors were encountered: