Erick Danzer

One more thought on this. The one other thing I could see here is if you were storing your template files here:

wp-content/plugins/nextgen-gallery/products/photocrati-nextgen/modules/ngglegacy/view/

That’s where NextGEN stores it’s default/included templates. But if you stored there and updated your plugin, your files would be overwritten, so if that’s the case you should avoid storing your template there. Instead, create a ngglegacy folder within your theme directory (wp-content/themes/[your-theme]/nggallery) and re-copy your templates there. Once they are in that folder, they should start working again.

Hi Kapara – received your email to Mike and I just sent a response.

Just for reference for others who may seeing a similar message at some point… the message is being generated in this case because the OP is using “template=galleryview” within his legacy shortcodes. For reference to that template to work, one would either need to have the NextGEN galleryview plugin installed and set up or have custom template files stored in a nggallery in your theme folder (wp-content/themes/[your-theme]/nggallery).

Neither of those exist, so the shortcode is referencing a template file that doesn’t exist.

@kapara – as noted in the email, you’d need to have the plugin installed or have custom templates in place in your theme folder for that shortcode to work. That template doesn’t come with NextGEN.

I’m assuming from your post that these were working recently for you? For them to stop working you’d need to remove the galleryview plugin and/or delete the template file from your theme folder. Updating NextGEN wouldn’t affect the template file since it’s stored elsewhere.

Do you know if you’ve made any changes of that kind to your site recently?

Which slider are you using? And how are your background images uploaded and added to your site? Assuming that you’re not using NextGEN for your slider or background images, it sounds like it would be a conflict with whatever is powering both of those.

Just want to second the thoughts here. I’m always amazed at how much time you all give, and how consistently. Very few people are willing to give that much constant time on a volunteer basis. And you do it in a sometimes difficult environment. I agree that WP, these forums, and the users in them are all lucky to have you.

@nfwro: Thanks very much for the update. Keep us posted.

@mellowvision: I think the issue you’re seeing is that template functionality does not currently apply to NextGEN Pro galleries. It’s just something that’s in place for basic galleries that are part of the NextGEN Gallery.

@nfwro: just one additional note. You mentioned the NG Custom Fields plugin. There may be some separate compatibility issues there affecting your templates until that plugin is updated for full compatibility with NG 2.0.

Hey all – this is Erick from Photocrati. I just wanted to jump in and respond to the questions from some of you about “if not templates, then what.”

First, I just want to reassure you that when we say we’re deprecating templates, it doesn’t mean we’re going to stop supporting them. Given how popular templates are in the NextGEN ecosystem, I just don’t see how we could ever consider that. So our intent is to continue to support the template functionality exactly as it exists now to ensure full backwards compatibility, and compatibility with templates going forward.

At the same time, we’re not going to be investing time to improve or refine the template system. And we are going to be working improving and developing the “module” system that defines much of the logic of NextGEN 2.0. Right now, you can add new gallery types to NG 2.0 using modules and this system is more powerful and flexible. But right now, it’s also more complicated than adding a template. So we need to refine the functionality and documentation to make it easier to add new gallery types via modules. We’ll know we’ve done a good job with that when people start using it.

Until then, you are welcome to continue using templates with the knowledge that we’re going to continue to support them.

–
Given everything I’ve said above, your current templates should be working and most templates are working. If they are not, that’s an issue or bug we need to address. The best thing you can do is submit a bug report with login credentials. We’d need to see your template and understand why it’s not loading correctly.

https://www.nextgen-gallery.com/report-bug/

@eyeqt: where are you storing your custom templates at? You can still store them in the theme folder, as will previous versions of NextGEN, and they shouldn’t be overwritten. If your templates are there and not loading, please let us know – preferably in a separate thread or bug report.

You can also store them in the plugin folder. If you are doing that, they will be overwritten, so you’d need to restore them each time. Once you restore, they should be fine.

FYI – I think we are eventually going to create an option to store/read custom templates in a separate folder in wp-content as we’ve done with custom CSS to ensure it’s update proof and theme-change proof as well.

@vera: You can access support for NextGEN Pro by logging in with your details at https://www.nextgen-gallery.com/login. Just click support and submit a ticket there. We’ll respond to your ticket via email and take it from there.

Hi Kili – This is Erick from Photocrati. Thanks for your thoughts.

Just wanted to post a note for you, as well as everyone else in this thread. If you got hit hard by this, you have a right to be angry. Heck, I’m angry and we did it. This was major, and it caught us as well. You have my personal apologies.

But what’s been going on for since the 2.0 launch definitely hasn’t been a random process of throwing —- at people. I published a letter just after the 2.0 launch trying to provide context for what happened and what we were doing:

https://www.nextgen-gallery.com/open-letter-to-the-nextgen-community-from-erick-danzer/

I think that still accurately conveys the situation immediately post launch. Since then, we’ve been in an extremely focused and high intensity push to resolve issues from the 2.0 update. And while there are still some major issues to sort out – especially with respect to use of transients – we’ve actually made huge progress toward stability. Almost every indicator that we track or that’s publicly available, as well as feedback from hundreds (or thousands) of NG users underscores that fact.

Indeed, one frustrating consequence of this latest episode is that it undermines the sense of progress we’ve otherwise been making.

In any case, I don’t want to minimize the issue. I know it’s major. And you definitely have the right to vent as far as I’m concerned. Just wanted apologize for and affirm the significance of it, while also providing some context.

Sorry that should be wp-content/gallery/ as in the content (gallery not galleries) by default.

Hi – if anyone else has this problem, can you please go to GALLERY > OTHER OPTIONS, and check that “Where would you like your galleries stored?” is set correctly as “wp-content/galleries/” (that is, that the / is included there?

It should look like this:
https://owely.com/71isalR

The issue you’re describing was triggered by an incompatibility either from a big update to WordPress or JQuery late last year (2012), and Photocrati issued an update/fix about a week or so afterwards. You are currently using 4.3, and the latest version is 4.5.1. If you update, to the latest version, this will be resolved. Hope that helps!

When you set your Home page to Home, the “Home” title will disappear automatically. It’s set to do that. There’s currently now way to remove the titles on other pages, but we’ll be introducing a no-title page template for this purpose in the next update (4.1).

To change the color of the title, you’ll want to go to THEME OPTIONS > CUSTOMIZE THEME > BODY and change your H2 heading font. You can adjust size, font style, and color.

Thanks1

Hi, the theme is designed to use a static page as the home page. It sound like this settings is not quite right for you. Sounds like you have a page called Home. You should also create a page called Blog. Then go to Settings > Reading, and set the home page to display a static page. Set home to Home and posts page to Blog.

When you’ve done this, the Home page will load as home, and the URL when you click Home will just be motionweb.co.uk/blog/ (no “/home-3/”). But just so you know, you can get rid of the “-3” by going to PAGES, then at the top click the “Trash” link to see the pages that are in trash. It sounds like your previous home pages are still in the trash. Delete them completely. Then try changing the URL back to /home.

Good luck!
Erick