nggallery.css: Slashes are missing

I don’t know if it’s because of DIRECTORY_SERPARATOR but even when I changed it to “/” I still can’t view my images…

Please look at the images source https://www.regle.com.pl/galeria

Sory for doubling

This error has been fixed in V 2.0.14! ??

I still have the problem !! no slashes in images url

this is the url of an image without slashes :
https://www.roulemans.net/wp-contentgallery24-heures-rollerthumbsthumbs_29juin009.jpg

and link to css :
<link rel=’stylesheet’ id=’nggallery-css’ href=’https://www.roulemans.net/https://www.roulemans.net/wp-contenthttps://www.roulemans.net/ngg_styleshttps://www.roulemans.net/nggallery.css?ver=3.6&#8242; type=’text/css’ media=’all’ />

So i will search errors in my localhost wordpress or migrate nextgen galery to wordpress galery and delete nextgen

Exact same problem here…
Mentioned HERE

It seems I’ve found fix for 2.0.14. It works for the home.pl hosting too.
The following file should be changed:
/wp-content/plugins/nextgen-gallery/products/
photocrati_nextgen/modules/nextgen_data/
class.ngglegacy_gallerystorage_driver.php

In line 170

'',

you can replace empty string with slash

'/',

You can also place DIRECTORY_SEPARATOR instead of slash:

169 trailingslashit($fs->get_document_root()),
170 DIRECTORY_SEPARATOR,
171 $this->object->get_image_abspath($image, $size)

___

BTW sometimes in admin panel tab Gallery/Other Options the following warning is generated:
Warning: strpos() [function.strpos]: Empty delimiter in /wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/fs/class.fs.php on line 62

It happens when
$this->get_document_root()
is empty string. The function strpos doesn’t like it.

In file class.fs.php from line 62 instead of

if (strpos($path, $this->get_document_root()) === FALSE) {
                $retval = $this->join_paths(
                    $this->get_document_root(),
                    $path
                );
            }

you can insert something like that:

$r = $this->get_document_root();
            if($r !== ''){
            if (strpos($path, $r) === FALSE) {
                $retval = $this->join_paths(
                    $r,
                    $path
                );
            }
            }

Thank you very much SylwiaFP!
Insert a “/” in the right place solves the problem.
It is a pity that the author of the plugin to version 2.0.23 not applied your fix,
with each update probably need to do it again.

Nice1 SylwiaFP :]

Hi all – Just directed to this thread from another thread and I don’t see a post here from anyone on the NextGEN team since @sylwiafp’s fix. We had introduced a fix for a separate issues causing missing slashes.

For now, I’ve asked our devs to take a look at SylwiaFP’s fix, and if it doesn’t cause other issues and we haven’t resolved it already separately, we’ll try to include it in our code in the next update.

@sylwiafp: thanks for much for taking the time to post a fix that seems to have resolved this for a fair number of users. It’s much appreciated. Thanks! (Erick)

STILL NOT RESOLVED
Unfortunately replacing the empty string with “/” in lne 170 of “class.ngglegacy_gallerystorage_driver.php”
just partially solve the problem…

Now it finds the correct path to pics but STILL miss all the rest.
Because of this in plugin/admin cannot make nothing and even in gallery front end CSS is missing / path is broken without needed slashes.
In my case it happens when i move website from “/tmp” to root.

In which other files should i place the “/” ?
Which file controls all basic paths of the plugin?

Not solved…
Maybe was not so clear before.
In my case problem appears when i moved the website from a “/folder” location to the root.

The trick of line 170 just partially solved the problem but gallery is not usable because css still missing and cannot admin/upload/modify anything ’cause all the header’s inclusions of plugin (js/css) are missing.

Slashes are still missing.
Someone can help?

@jamesfdfsf & @james_mm – This topic was six months old … although it may seem similar I would suspect the issues at hand are not and you should each create your own separate topic so we can fairly review them.

Thanks!

– Cais.