responsivemenu
Forum Replies Created
-
Hey Vitago,
Yes but the script works on your normal menu so Im lost as to why its not working with that woocommerce script.
I guess you could go through it line by line and see where it breaks, it maybe to do with the output buffering.
The only other thing I can think of is to change the priority number of the function, try updating the number 100 to 1000 or higher.
Its a long shot but its all I can think of at this moment.
Hey Charlie,
Great point my friend!
Will get that patched for the next update and thanks for pointing it out.
All the best
OK, I appreciate you pointing this out. By ‘banner’ do you mean an admin notice, or somewhere else? Never saw this myself.
There is an upgrade notice now that shows before upgrading from the 2.8 versions and also there is a banner showing in the plugin admin area for 2.8 versions.
It can be closed however so it wouldnt suprise me if people didn’t read it.
All the best
Hey xdividr,
My site was running PHP 5.6 and generated fatal errors on update.
As I said those initial errors have now been fixed and it was patched within a few hours of release. Unfortunately although I tried testing it as rigorously as possible some issues remained but were patched almost instantly. I hope no-one else will suffer what you have done and I can only apologise for that.
Core updates: disagree, old news. Since 3.7, by default, every site has automatic updates enabled for minor core releases and translation files.
I have all auto-updates disabled on my production sites, including translations and minor core updates. It may not be necessary for all but like I said, I dont allow any code changes to live sites that havent been tested on dev sites – even WordPress core minor updates have the potential to break things, even the best developers in the world can introduce unintended bugs that may not show up in testing.
However, you have some responsibility too. You took the time to make landing page for people with broken sites. If you know stuff will break, be cool and notify users via an admin notice in a minor version.
I 100% agree with you on this, I try to take as much responsibility as possible and have added Upgrade Notes before updating now for old 2.8.9 versions – I admit it was an oversight on my part and have tried to make it clearer for those who still havent upgraded along with the patches to stop the fatal errors I hope it will be a more pleasent experience now.
If you have any more tips or advice I am always open and willing to know more.
All the best
Hey vitago,
Just to confirm you have updated the script to the one I said with the return statement and not the echo.
I’m confused as it is working for me here. Can you try a simple version of the script to see if it works, for example:
add_filter('wp_nav_menu_items','responsive_menu_test', 10, 2); function responsive_menu_test($menu, $args) { return 'before' . $menu . 'after'; }That way I can tell if its something inside the actual script or my plugin on your site.
All the best
Hi bbikers,
In that case you will need to ask your host which PHP version that site is using.
Please let me know what they say
P.S – I don’t want it to sound like I am not willing to help out WordPress site owners.
In fact the opposite, you can probably see the amount of free support I offer people and I get about 4 times as much on email as I do here and respond to every one.
I always want to make developers lives easier as I am one myself. I took every possible precaution possible with the 3.0 release as I know major releases can be painful at first.
I made sure that all compatible settings were copied over when upgrading and placed banners for months about not upgrading to the 3.0 unless you have the right version of PHP installed.
Also, the error messages you originally posted have been patched since so you will no longer see these and it wont take sites down anymore so hopefully that will allievate much of the concerns moving forward.
All the best
Hi xdividr,
I’m afraid I will have to disagree with you on most of your points here.
Plugin auto-updates on live, production site should not be a thing and in my mind is the opposite of good practice. It is incredibly bad practice to have something like this in place on a production site.
You should 100% of the time have a development or local environment for testing plugin updates and making sure all is well before pushing to a live site. It sends shivers down my spine to see people carelessly update plugins or WordPress itself on live sites.
Anything can go wrong with a plugin update and people do make changes over time. If I never released a major update again then people would be even less happy as you would have a product that is left stuck in the past.
This plugin has been around for 3 years now, I think that one major update that only has a few differences is not actually as bad as you are making out to be. I understand the fact that it is no longer compatible with PHP 5.4 and below can be annoying to some people, but honestly that is an un-supported and un-secure version of PHP that PHP themselves don’t even support anymore, how can I possibly support it?
Even PHP have just released version 7.0, which has broken alot of backwards compatibility and will cause alot of plugins on WordPress to stop working. I am much happier that PHP have moved the codebase forward than get stuck in the past.
I understand there is work on the developers side to make plugins as compatible as possible but as I said the only way this plugin will break is if you are using PHP 5.2 which stopped being supported over 5 1/2 years ago.
All the best
Hi bbikers,
Your PHP version can not be on 4.5 as the last PHP 4 version released was 4.4.9.
Create a new page somewhere and simply add the following to the file, load it and see what it says:
<?php echo PHP_VERSION; ?>All the best
Forum: Plugins
In reply to: [Responsive Menu - Create Mobile-Friendly Menu] Strange things happeningHey there,
I can get on the site fine now.
Can you please give me steps to recreate the issue as I have clicked on every page of the site and have not seen any of the issues mentioned above as yet.
If you are getting white screens it sounds like a PHP or server issue somewhere – what is in your PHP logs for around the times that you see issues?
All the best
Hey there,
The margin from the title was removed as it was too overpowering but you can simply increase the size using the below custom CSS:
.responsive-menu-box { height: 47px !important; }Regarding the menu button changing colour on other pages thats because you have custom CSS to do that, as below:
.comment-form #submit, .comment-reply-link, .woocommerce .add_to_cart_button, .woocommerce .checkout-button, .woocommerce .single_add_to_cart_button, .woocommerce #place_order, .edd-submit.button, .page button, .post button, .woocommerce-page .woocommerce input[type="submit"], .woocommerce-page #content input.button, .woocommerce input.button.alt, .woocommerce-page #content input.button.alt, .woocommerce-page input.button.alt, .woocommerce-page .products a.button { background: #dd9933 none repeat scroll 0 0 !important; }Please remove this if you dont want the orange background on other pages.
All the best
Sure, you can get it from the Developers tab on the WordPress plugin main page.
You need version 2.8.9
Forum: Plugins
In reply to: [Responsive Menu - Create Mobile-Friendly Menu] Strange things happeningHowever before I can look at the site can you try disabling WordFence too to see if that causes the issues to go away as none of the things you have mentioned should be a side effect of my plugin.
For example we don’t touch the styling of the admin bar, we don’t stop pages from loading and we would never show a connection reset screen.
Of course I will take a look once I can access your site to see if I can find any obvious cause.
Also are there any errors in your PHP error logs or any WordFence logs as these will definetely help
Forum: Plugins
In reply to: [Responsive Menu - Create Mobile-Friendly Menu] Strange things happeningHey there,
I can’t get on your site as it is blocking me, the message is as follows:
Your access to this site has been limited
Your access to this service has been temporarily limited. Please try again in a few minutes. (HTTP response code 503)
Reason: Access from your area has been temporarily limited for security reasons
This response was generated by Wordfence.
Hi sanbdev,
I just checked this and it looks like more a problem with your site than my plugin.
If my plugin is deactivated does that front page image still stick out to the right? It seems to have a width of 119% so id be interested to know.
All the best