Reviving an old but very useful Wordpress Plugin - wordpress

I've been using this Wordpress plugin for many years https://wordpress.org/plugins/admin-post-navigation/
It had over 20,000 active installations and is certainly most useful for navigating between posts in the backend by simply clicking Next / Previous.
Gutenberg and Wordpress 5 unfortunately broke it and the developer of the plugin seems to be MIA.
My knowledge of writing or even trying to fix plugins is sketchy to say the last. I did some digging today using Developer Tools and I found that my favourite little post navigation buttons are there but forcefully hidden by Wordpress. Here's a screenshot of how I can make them re-appear but I'm a bit stumped how to make a change like this permanent or better yet try to make the plugin force it's way back into Wordpress 5 and Gutenberg.
I did make a feature request on Gutenberg which was promptly closed, seems they are not too interested in pleasing any advanced or long time users of wordpress. Surely such a navigation system cannot be rocket science.

Related

Search plugin breaking parts of theme

I've been asked to add a search function to a website. I'm trying this out on a testing site at http://www.somethingchronic.org.uk (the password to view is Entrand0s1).
I've installed a search plugin which works on all pages except the home page. On that page it clashes with the script in the slider plugin and when I tried deactivating the slider plugin I also lost the four large buttons at the bottom of the page which are part of the theme itself. Both the slider plugin and the theme are old but I'm hoping to keep the site going for a little while longer if I can. I asked for advice from the search plugin developer who said it's to do with the slider loading an older version of the jQuery library. I searched on here for jQuery library conflicts - one answer linked to the learn.jquery website with a list of options for avoiding library conflicts. There were a number of options for adding code - I tried adding some of these to the header.php document but each time the site broke completely and truth is I don't know enough about jQuery to know which is the correct piece of code to try. Any advice appreciated - would be great to know if there is a way to get the search plugin to also work on the home page whilst keeping the current slider. Many thanks

Product list randomly disappearing in Woocommerce shop page with W3TC

I manage a Wordpress page that had this issue before, but after doing some caching configuration (W3TC) the product list in shop page started disappearing more frequently. The only thing that brings it back is opening the page in page editor and pressing "update", no changes should be made. Purging all cache also does not help (pages are built using DIVI page builder).
So far I have reverted all of the changes that were made before, but that has not decreased the frequency of the issue.
Because of the store being live, I am not inclined to do plugin uninstalls as it can damage the page even more (Issues of page CSS not loading properly were seen before, purging cache helped in that case)
One thing that I thought about is making some kind of script that updates the page automatically as a temporary solution (a new site is going to be made eventually)
What could be done to either troubleshoot this issue in safe way or at least create an automatic page update script?
-WordPress 5.1.1 running Divi theme, Woocommerce version 3.5.7-
You say page "started disappearing more frequently", do you mean page is loaded but content disappears or it whole page does not load?
Try turning off Minifying in W3TC. I had this problem few times and always a problem was typo in CSS.
In W3TC in General Setting there is possibility to enable Preview mode, turn this on always before deploying. Turn on preview mode, check if everything is Ok, test, search for bugs. And only when you are sure that everything works fine then deploy it.
Thank you Vladimir for the tip about preview mode. The bug unfortunately is not in the CSS though because minifying is not enabled in W3TC.
By "disappearing more frequently" I mean Header and Footer being fine and Body being only partly loaded - Broken page screenshot
However, I have tracked down the issue to woocommerce itself. It seems like the default set shop page is the one crashing regularly. I did not find solution to the initial problem, but I found a trick that works, at least for now.
I created a new Shop page, but instead of linking it in Woocommerce settings, I just included a [products] shortcode. The previous page is still active, but not visible to user. Even if the shop page itself crashes, products are still visible and purchases are possible.

what will happen in my website when i changed the current theme with new one?

1) Can i change the theme of wordpress in this site
www.lenews.info
with this,
http://quanticalabs.com/wp_themes/pressroom/home-style-6/
2)if i do it i lost something of image article format etc??
i need to change the theme but i don't know if i do it, what happen in the site
3) if i change the template? i want the same format of plugin and component, can anyone help me with this?
Presently I am using a wordpress theme.
I want to change it to something better. But I am afraid, if I change
the theme,
I will lose all my contents that includes Posts, Pictures,
Categories, Tags.
I am not at all aware of this fact. Need some help.
Tell me if what I am afraid of is really going to happen if I change or not.
What are the pre-steps that I can take to keep all my contents uploaded the same way they were before.
I already have a daily backup system using WP Backup plugin.What else?
Please help!
Good habit is backup before do changes.
Checklist: 6 Things You MUST DO Before Changing WordPress Themes
Take Notes on Your Current Theme
Go through your theme files and note down all additional code that you added. You also want to check your current theme’s load time because this way you can compare the two. Go to a site like Pingdom Tools or use YSlow to test out different pages (Yes different pages, not just the homepage).
Be cautious of the Sidebars
If you are using a widget-enabled theme, and you switch to a theme that is not widget-ready, then you will lose all of that. If you are using a widget-enabled WordPress theme, then this is not an issue.
Also anything that you modify in sidebar.php file of your old theme, will be overwritten. So make sure that you add those codes in the new theme sidebar.
Backup!!
You never have anything to lose by creating a backup. As a precautionary measure, you should backup all of your theme files, plugins, and the database.
4.Testing all functionality and plugins
Once you have the new theme activated, you need to make sure that you retain all the functionality and plugins still work. Try out all the features including but not limited to the commenting process, single post pages, search, 404 page, archive page, contact page etc. Make sure all of your widgets are still there and are working.
Cross Browser Compatibility
Test your site in all browsers you have access to. Browsers have a tendency of rendering things differently.
Maintenance Mode
You probably don’t want your users to see while you are making the switch because they will end up seeing a broken site or such. It is best to turn on Maintenance mode for 15 – 20 minutes that it may take you to make sure that everything is working properly. Once you have setup Maintenance mode, you are good to go ahead and activate the new theme.

The famous Wordpress white screen of death

Like mentioned in the title, i think this is by far one problem Automattic or Wordpress team cannot solve until no matter what version Wordpress will go in future. In this question, i am focusing to the white screen of death that i get whenever i want to activate certain plugins. I am developing a site that requires me to use 30 plugins. Yeah, some will say thats too many plugins for a site, no wonder i will get the white screen. But hey, this is Wordpress, one of the reason that makes Wordpress the most popular blogging platform is because the availability of the plugins that can make you achieve your goal in less time. For those who expert in php+wp development, you guys can say hack the wp is better than using a lot of plugins like what i am doing but hey, majority of wp users are not php guru. Most of them are normal user like me or even just know how to install and use what are available to them.
So far, here the common steps we do when get the white screen of death (WSOD).
Rename the wp-content/plugins folder name such as wp-content/plugins-temp, this will deactivate all plugins
Like me, i prefer rename the individual plugin folder name, such as wp-content/plugins/akismet to wp-content/plugins/akismet-temp
After that, reactivate all the plugins one by one, so we can know which plugin is the culprit
Check for extra empty space at the end of the plugin file, especially after the php closing tag ?> make sure there is no extra space after the tag. Make sure check at the theme functions.php file (if any) or the plugin file.
Increase the memory allocation for wordpress
Usually, your site will be back to normal after that. BUT this will still not solve this problem.
For me, this is very annoying to me, especially the step number 3. How can we know which plugin is the culprit?? At the first place, i thought the step number 3 is really a fact but now i think its a lie. WHY?
Like right now, suddenly after i activate 25 plugins, one of plugin that i cannot reactivate is Akismet. What? Akismet? Yes, the plugin dev by the WP team itself. I know the step number 3 above is a lie because if i activate Akismet first, the Akismet is activated successfully. No problem at all.
So right now the problem is plugins compatibility among the plugins. How can me as a normal user can identify which plugin that is not friendly to what plugin??? If i am using 30 plugins, how many probabilities from one plugin is not compatible to each plugin???? how can i know which plugins should be activated first so the WSOD will not appear?
If there is error, then maybe i can have a clue, but its a plain white screen. I am clueless. This clash of plugins in wordpress is really an unsolved problem that makes me really stress.
Anyone know how to fix this? At least know how to activate the plugins via mysql?
Hello :) this my first answer I hope it benefits so many people because I suffered from this stupid problem and the solution was really awkward and I can not get it but it works.
I'm here to talk about the solution for the white screen of death that comes after logging in and you get this white thing instead of the admin panel what ever the user role was.
There is the common solutions as mentioned above. In my case I had only one plugin and I did a lot of changes on it. Also I edited the footer.php in wordpress. I found out the WSOD ( White Screen Of Death ) comes out after the first changes in one of the php files of the plugin. The way I used to do the changes is by editing the php file in my computer through text editor then I would upload the changed php through ftp to replace the old one and then the problem starts. Abd when I revert the step and return the original file every thing goes back to normal.
If you having this problem the solution would be very simple and I really don't know why no one have ever post it before.
The solution would be by simply putting your changes through the editor you have in the admin panel. There is two editors, one for the theme and the other one for the plugins.
Open the editor in the admin panel for the plugin you want to modify insert the changes that you want in the text editor you have in the admin panel web page and when you are done click on the update file button.
And happily you will end up with your modification and NO White Screen Of Death.
I hope you all a bright future with no more WSOD.
UPDATE: through researching and trying more , I found out that editing the files and Encoding it with UTF-8 will lead to the problem to avoide that edit the file and make sure the encoding is either ANSI or UTF-8 without BOM
You should try to run a version of PHP with xdebug installed. A WSOD, that's most likely a PHP parse error. So this isn't really a WordPress problem, it's a PHP problem.
Using xdebug helps, because you'll get a fancy stacktrace in some significant % of the cases where you otherwise would have gotten a WSOD.

Preview theme in drupal

I am using drupal for the first time. I have successfully developed my first drupal website to a certain extent. I have used my own custom theme for the front-end and blue marine theme for administrator. Now my client's requirement is that when he clicks on preview button before submitting the page in admin panel, he wants to see the preview in a pop-up window with the front-end's theme. Please help me with your ideas and suggestions on how to achieve this?
When you set the administration theme, leave the "Use administration theme for content editing" unchecked. This should allow content creation / previewing in the "front-end" theme.
EDIT: Assuming you are using Drupal 6.x
Have you seen this module - http://drupal.org/project/pagepreview it aims to give you what the page will look like on the front-end theme.
There are some caveats though, for instance the menu will not be correct if this is a new node
As far as I know Themeing is a complicated process in Drupal, it involves many modules and hooks, so I don't think it's an easy task for a module (maybe) to do that, or in core like Wordpress.
I'm working on getting a nice solution to this too. I won't post the code yet cos it's a work in progress, but essentially I make an ajax call to retrieve a known node and then replace the node content of that page with the content of the preview box before showing the merged page in a popup window.
If it works out alright I might make a module out of it.
This might help: https://www.computerminds.co.uk/drupal-code/making-accurate-responsive-node-preview-drupal-7
Patches the Page Preview module with some of the Responsive Theme Preview modules functionality for viewing the page at different screen sizes in the preview panel.
Page preview's caveats still apply though.

Resources