markob17

[markob17]

In theme options I believe there is place to input your envato/theme forest purchase code. Then theme updates happen like any other theme update, via WP dashboard. It id in the Kleo documentation.

[markob17]

Hi @sharmstr, I’m trying to figure out how to make your code below only change the breadcrumbs on posts. I want all other pages to use Kleo breadcrumbs. Is this possible? I tried an if statement using is_single() but doesn’t work for me. My coding experience is limited so I’m not sure what else to try. Thanks for your help.

COPY CODE

function kleo_breadcrumb( $args = array() )
    {
        return WPSEO_Breadcrumbs::breadcrumb( '<div class="kleo_framework breadcrumb">', $after, '</div>' );
    }

Regards,
Mark

[markob17]

Happens on all mobile resolutions. I actually found an existing thread on this support forum that provided a CSS solution that fixes this issue. It is below. However, I believe on that same thread you guys said this css fix would be incorporated into later Kleo updates yet it still occurs, so appears it slipped through the cracks. Maybe something to add to your timeline for the next Kleo update.

COPY CODE

.panel-kleo.icons-to-left .accordion-toggle {position: relative; display: inline-block;	width: 100%; padding-left:30px;}
.panel-kleo.icons-to-left span.icon-closed, .panel-kleo.icons-to-left span.icon-opened {position: absolute; top: 1px; left: 0;}

Regards,
mark

[markob17]

Hi, looks like this css fix resolves the issue, however, it still hasn’t been added to kleo updates. I am running latest version (march 2016 version) and the issue still occurs if I don’t manually add the css in this thread.

[markob17]

Thank you for looking into this and for adding the fix to your next release.

[markob17]

All plugins are updated. Not sure why I’m still receiving the message. Any ideas?

[markob17]

Hi Guys. Any update on this? I am still receiving this message and Kleo has already had multiple updates since this thread.

As of now I have to manually view the code to change the element on toggles, for example to make them closed upon page load. I used to be able to before this error occurred change the “active section” to collapse all accordions by default within the Kleo Accordion Settings box.

[markob17]

Interesting. Not working on my installation. No plugins enabled except buddypress and bbpress. Latest version of Kleo and latest version of Crayon Syntax Highlighter. Also, latest buddypress and wordpress. Everything looks like the screenshot I’ve attached. PHP opening and closing tags don’t look right. Is it possible it has something to do with my server?

Thanks,
Mark

Attachments:

You must be logged in to view attached files.

[markob17]

Hi,

Thanks so much for looking into this. I am going to try out your suggestions later on today when I get done with work and will be sure to let you know what happens. Also, I had submitted a ticket with Buddypress.org for this same issue which you may want to take a look at. There is some important information your developers may find useful. I was given a solution to get custom member loops to work by one of the Buddypress.org guys. Check out that thread here and forward it to your developers for it may be useful:
https://buddypress.org/support/topic/possible-bug-when-displaying-a-members-loop-above-cover-image-on-member-profile/

Regards,

mark

[markob17]

I’m adding the following code to the general-before-wrap.php file just after do_action(‘kleo_before_content’); section. You can also add it to other places in the theme, doesn’t matter for it breaks the private message button anytime a member loop (kleo carousel or custom) is displayed above the cover image header regardless of how it is added.

COPY CODE

<?php if ( bp_is_member() ) { ?> 
<div class="member_avatars">
<?php echo do_shortcode('[kleo_bp_members_carousel type="active" number="5" min_items="2" max_items="7" image_size="thumb" rounded="rounded" autoplay="yes" online="noshow" class="customclass"]'); ?>
</div> 
<?php } ?>

For example, you can also add it via a fairly standard way of showing a custom members loop and the same thing occurs. Here’s the code I used in that testing scenario.

COPY CODE

<?php if ( bp_has_members( 'type=newest&max=6' ) ) : ?>         
                    <?php while ( bp_members() ) : bp_the_member(); ?>                      
                        <a href="<?php bp_member_permalink() ?>"><?php bp_member_avatar('type=full&width=125&height=125') ?></a>
                    <?php endwhile; ?>
<?php endif; ?>

Basically, anytime a members loop (kleo carousel or custom) is run before the cover image header ( notably the <?php do_action( ‘bp_member_header_actions’ ); ?> section of that code ), the private message button breaks.

[markob17]

NOTE: I am using default Buddypress Cover Image functionality if this helps.

[markob17]

If you view the site in responsive layout at smaller resolutions (iphone, android, ipad, etc.,) there is spacing issues for example. So yes, I’d say this is the case. For example, if you look at the attached screenshot you will see the spacing differs on the left and the switch to view another profile button overlaps the header and any other element as you scroll down the page. I’m assuming you had spaced it at 17.5 on both sides to prevent the overlap in the first place. Not sure why the 17.5px value is missing on the two aforementioned items with the latest update.

Attachments:

You must be logged in to view attached files.

[markob17]

I wanted to inform my slowdown issues seem to have went away. I am not sure if it was caused by load on my server today as I run another website on it and I am only using a VPS, or if it was fixed because I cleared the cache on cloudflare and wp super cache, and also disabled and re-enabled all plugins. I also upped the WordPress memory limit from 256 to 512M just in case.

[markob17]

This is unrelated but I noticed some CSS styling is missing from app.css/app.min.sss in the latest release of kleo. It’s an easy fix, however, you may want to fix it in the next release. The code below shows what is missing.

COPY CODE

.page-boxed .sidebar-right .inner-content {
    padding-left: 17.5px;
    padding-right: 17.5px; - THIS IS MISSING IN KLEO 4.9.1
}

.page-boxed .template-page.tpl-right .wrap-content {
    padding-right: 17.5px;
    padding-left: 17.5px; - THIS IS ALSO MISSING IN KLEO 4.9.1
}

[markob17]

May I ask how many members you have? Also, what kind of server/hosting? Heard buddypress in general needs robust hosting.

Thanks.

[markob17]

You should be able to fix it by using ftp to access your server and editing the .htaccess file. Within that file you can delete the following:

COPY CODE

# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
#If you serve pages from behind a proxy you may want to change 'RewriteCond %{HTTPS} on' to something more sensible
AddDefaultCharset UTF-8
RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{HTTPS} on
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-https.html.gz -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-https.html.gz" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{HTTPS} !on
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html.gz -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html.gz" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{HTTPS} on
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-https.html -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-https.html" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{HTTPS} !on
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html" [L]
</IfModule>

# END WPSuperCache

If it is still broken, you may have to remove the (BE SURE TO BACK THEM UP FIRST) advanced-cache.php file and possibly the wp-cache-config.php (will lose your settings though by removing wp-cache-config.php) from the wp-content directory. Once that is done the site should work again. If not, deactivate WP Super Cache before making these changes. AFter this is done, you can reactivate the plugin and re-set it up.

[markob17]

scottmriley – I’m not sure what it is. I am always quick to blame a new theme update but could be a plugin that needs to be updated to be compatible with the latest release, or maybe my server is slow today or something throwing me off, I did recently get spammed on another site hosted on my VPS. I’m going to wait and see for the next day what happens. For example, I use Geo my WP and the Kleo add-on for geo searches in my members directory, so could be that for all I know. Either way I am frustrated. If my site was production right now I’d be very hesitant to install any theme updates right away, especially without thorough testing. I’m still toying with Super Cache to get it to work as we speak. I have it setup mod_rewrite and to not cache for logged in users, seems to mess things up when caching stuff for logged in users. I use it for my blog pages mainly that will be open to the public, but not for member pages, activity stream, etc. If you find anything out, please let me know, and I will do the same. Thanks.

[markob17]

I just updated to Kleo 3.9.1 and now my site is super slow as well. Like really slow and I never had this problem before updating to 3.9.1. 3.9 there was no slowdown, but 3.9.1 slowdown started occurring. Ugh. What has changed from 3.9 to 3.9.1 that could cause my site to slow to a crawl? Nothing else has changed. This is frustrating.

[markob17]

Hi Laura,

I am using the Buddypress cover photo feature. Just installed Kleo 3.9.1 and that update fixed my issue. I had reported this on the Theme forest support site yesterday after installing 3.9 so appears they were able to implement the fix in the 3.9.1 release. This ticket can be resolved.

Thanks,

mark

[markob17]

I encountered that awhile back and I believe it had to do with the thumbnail settings. I’m not 100% sure, but I think I had to make sure I had at least 150×150 thumbnails enabled in the settings>media in the dashboard and also had to run a plugin called regenerate thumbnails to fix it. Good luck.

Attachments:

You must be logged in to view attached files.

[markob17]

Hi Radu,

So that you can resolve this in the next release of Kleo ( in case you guys aren’t yet aware), I wanted to inform you that some layouts do in fact break with the latest version of WooCommerce and the current version of Kleo. I noticed the “for sale/products” when viewing a category don’t look right on responsive resolutions (looks fine on full screen view though). There is a random spacing above items as you will see in the attached screenshots. I tested this by using the default version of the Kleo theme without any modifications so it doesn’t appear to be isolated to my install.

Regards,

mark

Attachments:

You must be logged in to view attached files.

[markob17]

Sounds great Andrei. Thanks!

[markob17]

Is this fix still on your road map?

Thanks

[markob17]

Wish there was a solution, but so far I haven’t found one myself. Was totally annoying. I ended up removing paid memberships pro and manually setting up my own membership site via functions.php, etc. Paid memberships PRO seemed confusing to me, offered way more features than I really needed, and required me to pay for extra features anyways. If you’re interested in a very basic membership type site that offers free signups at first, check out below.

I’m basically offering a simple free signup for my users at first to increase signup rate but in order to get extra features (ad free, chat features, etc.) they will have to pay. I found the code below on WPMUdev if anybody is interested in setting up their own basic membership site without using yet another plugin. It’s a good starting point for locking down your site manually. I locked down everything except the home page, blog, and store. Everything else redirects to my custom register page. – http://premium.wpmudev.org/blog/how-to-build-a-facebook-style-members-only-wordpress-buddypress-site/

Anyways, still hope this issue gets resolved for I may want to use Paid Memberships Pro in the near future. Good luck!

[markob17]

No worries Andrei. Apparently something has fixed this issue more recently as I just tested, could be either a woocommerce update or a theme update from you guys. The workaround I was using was disabling Manage account in Buddypress setting in the theme options woocommmerce page. When that was enabled it was taking me to the manage account page when using the sidebar login, however, enabling that setting now no longer has that effect. Must be a recent update that fixed it. Thanks.

[markob17]

Hi Laura,

Had that enabled but doesn’t make a difference. I actually just figured out how to make it do what I want via CSS. The sidebar is now below the post when viewing on the iPad with a 768×1024 screen resolution. Just in case anybody else wants to do this, here’s the code I used:

@media only screen and (min-width: 766px) and (max-width: 769px) {
.template-page.col-sm-9 {width: 100%; border-right: none; margin-top: -15px; }
#main-container>.row { display: inline; }
.sidebar.sidebar-main.col-sm-3.sidebar-right { width: 100%!important; border-left: none; }}

Thanks for your help.

Mark

[markob17]

Hi Laura,

Unfortunately the site is running on a local machine in my network and not connected to the web yet. When viewing your Kleo demo online the same thing happens so you will be able to troubleshoot using it. Probably default behavior but I’d like to change 768px breakpoint a few pixels to make the sidebar go below the post, similar to the way it looks on resolutions below 768px.

Capture 1 shows what the site looks like on an iPad at 768×1024 pixels, capture 2 shows what it looks like on resolutions smaller for illustration purposes. I pretty much need to change Kleo’s breakpoint from 768px to 769px so that things triggers sooner and thus the sidebar will display below the post, similar to Capture 2.

Thanks,

Mark

Attachments:

You must be logged in to view attached files.

[markob17]

Hi, do you have an ETA on this? I am soon launching a new site and come launch would like my members to be able to use the Buddypress 2.4 core functionality from the beginning to prevent any confusion or potential future issues. I also personally don’t want to rely on another plugin for functionality that is built into Buddypress core.

[markob17]

Hi,

I am using the latest version of Kleo. Where do I have to put that code?

Thanks!

[markob17]

Thank you very much for the info. I was able to change the related posts images per your instruction.

You didn’t provide the instructions to change / override the 672 x XXXX for Post thumbs, and 1038 x XXXX for full width images, however, I was able to use your other function to understand the structure a little bit. I’m not a coder but was able to figure out how customize the default Kleo thumbs using a function I pieced together using your data.

It seems to work great for my limited needs (not using all fancy features of Kleo) and now my HD space won’t get filled quick. I had to customize the rtMedia and WooCommerce images in their settings page to match the rest of the themes sizes so now instead of 13+ images uploaded for each single image upload there is only 3 uploaded ( the 480×270, 150×150, and original). Anyways, here’s the function just in case anybody else with more limited needs like myself or who are concerned with disk space wants to try it out. Naturally it will have to be tweaked to meet their needs.

/** Function To Override Kleo Thumbnails **/
function kleo_thumbnail_overide() {
add_theme_support( ‘post-thumbnails’ );
set_post_thumbnail_size( 480, 270, true ); // Now Fixed Height And Width
add_image_size( ‘kleo-full-width’, 0, 0 ); // Disabled this size
}
add_action( ‘after_setup_theme’, ‘kleo_thumbnail_overide’ );

NOTE: The only other thing I had to do to prevent additional images from being auto created when viewing the blog masonry or other view (I am only using masonry for my blog) was to make a quick edit on the post-content-masonry.php file in my child theme. I added the following under the kleo_get_post_thumbnail_url() section to force it fixed height and width instead of dynamic height:

$image = aq_resize( $img_url, $kleo_config[‘post_gallery_img_width’], $kleo_config[‘post_gallery_img_height’], true, true, true );

Anyways, hope this helps anybody else out. For me, 3 images to server is better than 13+. Thank you again for providing the data to change the featured post images, wouldn’t have figured the rest of this out without it.

[markob17]

That’s a bummer as I hate to rely on another plugin, however, I just found this amazing plugin after doing some research and it not only resizes images to a specified size but also can compress them at the same time. It also does other things like bulk resize images already uploaded. – https://wordpress.org/plugins/imsanity/

Thanks,

mark

[markob17]

Hi Wualia, can you please tell me how you were able to fix this issue? I too already have that entry in my WP-Config but the error message is still there. I looked all over and can’t figure it out. Thanks for your help!

[markob17]

Hello, I am having this same error. My WP-Config already has that entry and the issue is not going away. Any ideas what else could be causing this problem?

Attachments:

You must be logged in to view attached files.

[markob17]

Thank you Laura. Looking forward to them providing a solution. Thanks!

[markob17]

Hi Laura, as I mentioned already, the option is already set to reload current page. This doesn’t work for the widget login, only the menu driven pop up login. Please advise? However, it does work for a custom page interestingly enough. Any idea why it’s not working when set to reload current page? This is preferable. Thanks.

[Author]

Posts