iDesignCo
Forum Replies Created
-
@photocrati – solved it. when the galleries were moved over, they somehow ended up with root:root as owner:group. That was keeping the plugin from generating the proper image for the previews.
Thanks!
@photocrati – Just tried both of those to no avail. The galleries load fine, but the URL that the albums are trying to load as their thumbnails is not. And it’s completely different than any other url the galleries use.
Any ideas where the
/nextgen-image/2759/91x68/crop/a32f84b2ca25d528182dd54a02681496URL is coming from? None of the galleries use a similar structure for their thumbnails or images. And the old site used a different URL than both the galleries and this new one for the album thumbnails.I’ve yet to come across a setting to configure this.
Thanks!
iDesignCoJust ended up having to relook at my solution here after updating the plugin again. I attempted to use the ‘override thumbnail settings’ option, but it never saves the info/option when I click save. When I reload the settings page, it’s set back to “no”.
So I just edited the hardcoded option in
modules/nextgen_basic_album/adapter.nextgen_basic_album_controller.phpagain.Okay. After spending some time searching the internet and playing around with files inside of nextgen, I found what I needed to change.
That size (91×68) is hardcoded into
wp-content/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_album/adapter.nextgen_basic_album_controller.php
When I change the size there, it all works fine. I feel like that’d be a good thing to have as a changeable option. The 91×68 is for legacy templates, but I had used my own customized templates back then, which used the thumbnail size of 250×285, not the default 91×68.Thanks!
Hi Seahawksean,
Thanks for your help. The thumbnail settings are correct. The galleries display with the proper thumbnails, but on the album page, the “gallery thumbnail” is grabbing the dynamic file and not the thumbnail file for the image select. And the dynamic file is 91×68 and I haven’t found a place to change that setting yet.
Any ideas where it is getting 91×68 from, and if there is a spot to change it?
Thanks.
Hi,
Just wondering if anyone saw this and has any ideas.
Thanks.
Forum: Plugins
In reply to: [WP Finance] Multisite IssuesThere are additional references to the user table, so instead of just on those two lines, replace any instance of
$wpdb->prefix."userswith$wpdb->base_prefix."users.That’ll make it all work for multisite.
-Chris.
Forum: Plugins
In reply to: [WP Finance] Multisite IssuesGood news.
I figured out the issue. It was in
/wp-finance/components/wpf_default.phpYou use
$wpdb->prefixto grab the table prefix for the site, which works fine for everything on a single-site installation. However on a multisite installation, you’re trying to use it for users, which is what’s breaking this.It’s trying to load
wp_3_userswhen it should be loadingwp_userson a multisite installation. Usingwp_3_as the prefix works for the rest of the time, because thefinancetable is with that prefix, but the users table is still in the main WP table.So by changing in lines 138-139 in that file from:
$wpdb->prefix."usersto$wpdb->base_prefix."users
to select the users instead, the plugin loads content fine in a sub-site.Hope this helps anyone else with this issue.
Chris.Forum: Plugins
In reply to: [Scebo - Customer Support] Scebo changed my CSS styleHey,
I ran into this issue myself, and it is caused by not checking for the ticket post type when queuing up the Admin CSS. They catch the post type for the edit.php page, but don’t check when it is post.php.
Making line 97 in the scebo/index.php file (the main one when editing the plugin via the WP Admin) look like
if ($pagenow == 'post.php' && $post_type == 'tickets')
will sold your problem.Forum: Plugins
In reply to: [Repository Zip] "Fatal Error" on Activation (Activation Fails)Nevermind. My server was set to 5.2 for some reason.