• Resolved redhawk07

    (@redhawk07)


    Hello,

    I created a page that displays an extended basic album. The selected album itself again contains two albums.

    Whenever the slug for this page contains (or at least begins with) the slug that’s set in the NextGen Gallery options, the page itself can be shown, but any displayed album gets a corrupted link. Here’s an example:

    Page name: Galerien
    Page slug: galerien
    Slug in NextGen-Options: galerie
    Created URL for the albums that are displayed on this page:
    /galerien/galerie/n/<albumname>

    These URL’s will not work and immediately redirect to the front page of the site.

    For the moment, I changed the NextGen Slug to “gallery”. Then, the links are created correctly and everything works fine. But originally I’d like to have the slug in German, because it’s a German-only page.

    For your tests, I created a “misspelled” page displaying the same content as the original page:

    URL: http://fotovereinpassau.de/gallerys
    This page slug “gallerys” now again contains the NextGen slug “gallery”. This leads to album links like http://fotovereinpassau.de/gallerys/gallery/s/fotosequenzen-2010.

    The correct links should look like this one:
    http://fotovereinpassau.de/gallerys/gallery/fotosequenzen-2010

    Regards,
    Stefan

    My installation:
    Site address: http://www.fotovereinpassau.de
    Wordpress 4.4.1 is installed on an Apache server in a subfolder, site address is the root folder.
    NextGen Gallery 2.1.23
    Other plugins (all at the newest version available):
    Add Meta Tags
    Antispam Bee
    Easy FancyBox
    Event Organiser
    Google XML Sitemaps
    MiniMeta Widget
    Page Builder by SiteOrigin
    Secret Content
    SecSign
    SendPress Newsletters
    Simple Image Sizes
    WordPress Importer
    WP Dashboard Notes

    https://wordpress.org/plugins/nextgen-gallery/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @redhawk07 – There could be a plugin conflict going on here or at least it should be ruled out; I am not familiar with all of the ones you have listed. Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?

    If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.

    Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.

    If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.

    Thanks!

    – Cais.

    Thread Starter redhawk07

    (@redhawk07)

    Hello,

    because it was easier for me, I created a completely new WordPress site with all the newest versions of WordPress and NextGen plugin. Theme is TwentySixteen.

    The problem is exactly the same as described in my initial post.

    Both sites are run on an Apache server. The test site is run on MAMP with PHP 7.0.0. The previously described site is run on PHP 5.3.17.

    If you need more info, please let me know.

    Best Regards,
    Stefan

    Plugin Contributor photocrati

    (@photocrati)

    @redhawk07 – Are you using the default MAMP ports, or are you using the Apache defaults? The best method is to use the Apache default ports (80 and 3306 respectively for localhost and MySQL).

    Thanks!

    – Cais.

    Thread Starter redhawk07

    (@redhawk07)

    Hello,

    in MAMP I had the default MAMP ports. I switched it to the Apache default ports, changed the settings in the wp_options table (options “home” and “siteurl”), refreshed the wordpress page containing the album, but there’s no change.

    Best Regards,
    Stefan

    Plugin Contributor photocrati

    (@photocrati)

    @redhawk07 – Generally if you change the ports in the local environment it is usually best just to create a new WordPress instance and move any content over as needed.

    – Cais.

    Thread Starter redhawk07

    (@redhawk07)

    Hello,

    As you suggested, I dropped the whole installation and created a new one which from the beginning uses the Apache default ports.

    Result: Same as in my initial post.

    Please have a look at this issue.

    Best Regards,
    Stefan

    Plugin Contributor photocrati

    (@photocrati)

    @redhawk07 – I’m not able to recreate this issue in a MAMP install … are there any more details you may be able to share related to this issue?

    Do you still see the issue if you move the site to a remote location?

    – Cais.

    Thread Starter redhawk07

    (@redhawk07)

    Hello Cais,

    Yes, the problem is the same. You can see it at this page:
    http://testngg.fotovereinpassau.de/galerien/

    Please check the link behind the displayed thumbnail.

    Best Regards,
    Stefan

    Plugin Contributor photocrati

    (@photocrati)

    @redhawk07 – Thank you very much for all of your efforts and our apologies for these inconveniences.

    Please send us a Bug Report (http://nextgen-gallery.com/report-bug/ … please reference this topic) so we can get a better look under the page at your site.

    Please include as many details as you can about your site and the issue at hand so we can move on this as fast as possible.

    Thanks!

    – Cais.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Permalink problem if pagename contains slug value’ is closed to new replies.