Here’s an easy jQuery fix for anyone having trouble making columns or sections links. Just give your column a class of “click-child”, then add this code:

jQuery(document).ready(function() { jQuery("body").on("click", ".click-child", function() { var href = jQuery(this).find("a").attr('href'); window.location = href; }); });

It’s really that easy. Be sure to include jQuery on your site prior to enqueueing this code to avoid errors.

The post Elementor: How To Make A Column or Section A Link appeared first on Ideas and Pixels.

I did find a few features lacking though. Things that should probably be built in are still missing, but hey, I’m sure they’ll get to it eventually. I guess I could get off my ass and contribute, as well.

Here’s my contribution. A simple plugin that allows you to select a theme template file from an Elementor widget and embed it in your Elementor document. I think it’s best to stay in Elementor the whole time, if possible, but there are some instances when it really slows you down (for more complex sections). This allows you to bypass that and develop the good old fashioned way. Enjoy!

Click here to download Elementor Template Element

The post Elementor Template Element: Basically get_template_part() As An Elementor Widget appeared first on Ideas and Pixels.

I’ve used WordPress ever since. Fast-forward to today, and I would venture to say I’ve probably made just south of half a million dollars on WordPress’s back (and I’m only 29). It’s been a godsend to me and my family (it’s allowed me to build a family, even as a third year college dropout) and the constant shortcuts with plugins and hooks and the event driven infrastructure that make it so unique (and that *real developers* love to rag on) has a real place in my heart. If WordPress never changed, I probably wouldn’t care. WordPress is possible only because of it’s almost always backwards compatible implementation. This has allowed websites to trust the platform and build with longevity in mind.

WordPress rebuild on Node.js

There were whispers throughout the community in the early part of the decade about WordPress development transitioning to Node.js. While I, too, was fascinated by Node at the time, I knew there was no way that a backwards compatible software like WordPress would make such a drastic change. Especially when that change would feature both a complete language and architecture overhaul. It couldn’t happen. It wouldn’t happen. It was then that I understood that WordPress will exist for a long time in the same code base it always has. And that’s not such a bad thing, really.

Will WordPress ever be overhauled? What should be changed?

WordPress probably will never be overhauled entirely. It will transition to the API as an option at first, then as a requirement over time.

Does it have to be a code structure overhaul? Do we need to implement more modern standards if the ones we have facilitate us so well? I don’t think so. But I do think we can already see the future of WordPress by looking at the API system. The API is clearly a big part of how things will transition in the future. You see it with the API integration in WordPress.com and Calypso. This is clearly the way things are heading. And I like it. It’s going to give us the ability to add an optional layer on top of our working infrastructure.

Gutenberg is also a great step.

Gutenberg fits in great with the trend that many WordPress developers have been going to as of late: using a pagebuilder plugin for content and structure management. While I was initially resistant to this, instead favoring an Advanced Custom Fields with Custom Post Types approach, I realize that I was wasting a lot of time creating interfaces that really didn’t need to be created in the first place. I tried implementing Visual Composer on a site from scratch and it actually went pretty well. Then I tried Elementor and I was blown away. It didn’t feel hacked together like the other pagebuilders I had researched and tried (looking at you especially, Cornerstone). After building a few sites with it, it’s become clear to me that this is the future of WordPress development, whether I liked it or not.

One thing truly needs change: the post-based content system.

While the uses of which are very clever and rather broad, the fact that every bit of content that goes into WordPress is stored as a post is clue enough that the platform’s blog roots are still the heart of everything. But to be honest, 80% of the sites I build for clients don’t even use the default Post post type at all. It just sits there or we hide it with another plugin.

This, and the merging of very unlike pieces of data in database tables, will always limit WordPress’ ability to be a full CMS without the help of many advanced plugins. WordPress is essentially is a mail boy who moonlights as a CEO. It’s built to write blog posts, but most of the time it runs entire websites. In fact, I’ve only made a handful of blog-only sites myself in all my years working with it. It’s a very understandable problem that it has, given the origins of the platform, but that doesn’t mean we must live with it forever.

Conclusion

For WordPress to really live up to it’s full potential, it’s going to need to become more than it is. It’s going to take Gutenberg, and structure changes, and the full integration of ideas like Elementor (which is seems like Gutenberg is positioning us to move toward). Until then, I will still use it on every non-technical project my company gets, but I do hope for an even better future where we innovate while staying mindful of where we came from.

Thoughts? Opinions? Please comment below.

The post When Will WordPress Be Overhauled (or Rewritten)? appeared first on Ideas and Pixels.

When working with WordPress, you will find out fairly quick that it can be pretty sensitive during updates and host transfers. This may create tension with the main reasons why you chose to use WordPress for your website in the first place, for example our issue being the Media Library. Our problems occurred during a server transfer for one of our clients. We realized that a lot of people were having this same issue, but no one had truly addressed it. Below are the steps to take when you find the WordPress Media Library not working correctly.

Problem | When trying to upload a new image to the WordPress Media Library it does not work.

Steps we take to solve this problem: These steps were taken and could potentially work at any given step so, you need to see if your Media Library works after each one.

Step By Step Guide Towards WordPress Media Library Not Working Properly With Solutions

WordPress 4.9.2 Media Library Not Working Fix:

PLEASE NOTE: I have not tested this, but I found this for the 3.9+ media library not working and apparently it involves the WP_Image_Editor default to GD. Add this snippet of code your functions php file:

function ms_image_editor_default_to_gd( $editors ) {
$gd_editor = 'WP_Image_Editor_GD';
$editors = array_diff( $editors, array( $gd_editor ) );
array_unshift( $editors, $gd_editor );
return $editors;
}
add_filter( 'wp_image_editors', 'ms_image_editor_default_to_gd' );

Source Default To GD

If this does not fix your WordPress library, delete the code you put into your functions php file (that is if you tried it) and follow this list of solutions that I have developed over the years!

Step 1: Disable all of your plugins and test to see if your media library is working. Now test to see if your Media Library is now functioning: (If it is working then go through and activate each plugin one at a time and see which one it is breaking your media library, then do not use it. Likewise if this does not solve the problem go to the next step)

Step 2: Log into your admin panel.

Step 3: Go to Settings > Media

Step 4: In the first writable field (Store uploads in this folder) it will state that the Default is wp-content/uploads but, it will not register this as “True”.

Step 5: Type “wp-content/uploads” within the field. (Also, make sure that “Full URL path to files” is blank.)

Step 6: Click, Save Changes. Now test to see if your Media Library is now functioning if not go to the next steps:

Step 7: Open up your File Transfer Protocol or (FTP).

Step 8: Go to your wp-content section. This will be listed within your sever at YOUR-SITE .COM/wp-content/

Step 9: Right click or highlight your “uploads” folder. If you do not have one then create one and test to see if your Media Library is now functioning. You need to have a folder here at YOUR-SITE .COM/wp-content/uploads/

Step 9 UPDATE ADDITIONS (1-25-2018): If you do have an “uploads” folder add a dash into the folder name by renaming it to “-uploads” and then making a new folder called “uploads”. If something is going on with the current folder this will let you know and your images will be backed up in the new folder called “-uploads”. Next copy/paste your image folders into the new “uploads” folder one at a time. If the old folder or a file in that folder was corrupt you will find out!

Step 10: If you have an uploads folder already or created a new one lets investigate the folder permissions. In your FTP migrate to this folder and right click on the folder to select its “File Permissions”.

Step 11: Set the Numeric Value to 755 or 777 (777 can present a security risk see details below). Now test to see if your Media Library is now functioning if not go to the next steps:

Step 12: Go back into WordPress.

Step 13: Go back into Go to Settings > Media

Step 14: Uncheck “Organize my uploads into month- and year-based folders”.

Step 15: Click, Save Changes. Now test to see if your Media Library is now functioning if not go to the next steps:

Step 16: Still have your hair? We will figure this out. Let’s Go back into your File Transfer Protocol or (FTP).

Step 17: Right click or highlight your “wp-content” folder.

Step 18: Select “File Permissions”.

Step 19: Set the Numeric Value of this directory to CHMOD 744. Now test to see if your Media Library is now functioning and hopefully it is by now. Please note if your website is still down, it could potentially one of two things. The first being a plugin that you chose or created. Most free plugins do not take in consideration that your site matters. It is a pain, but do some research on the person who uploaded the theme and be sure that you check their reviews. The second reason could be due to some of your folder permissions — they might have been lost during a host transfer.

Step 20: UPDATE ADDITIONS (2-12-2018): Sometimes you will require more memory with your host as WordPress eats up a lot (GoDaddy seems to have this issue and I highly recommend switching to Bluehost). If you plan on staying with your host navigate to your wp-config file and add the following code:


define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '256M' );


If this does not work try to increase the memory in the .htacess file by navigating to it and typing in this code:

php_value memory_limit 256M

Still no luck? Let’s try to add the PHP.ini file. Keep in mind this file, by default, is hidden and you may need assistance from your hosting company. If you are using a program, like FileZilla, make sure the show hidden files box is checked (This file will be found in the same areas as the PHP.ini and wp-config files are located):

memory_limit = 256M ; Maximum amount of memory a script may consume (64MB)

Step 21: If these solutions don’t work double check your .htaccess file and make sure this file matches with the theme you have installed on your site. Sometimes if this is not setup correctly it will re-write the path of the uploaded image. This is something you will have to investigate on your own and you can click here to fix your WordPress htaccess file.

Step 21 1/2:Have you recently transfer your website to a new host or copy a theme over to a host? Now your WordPress images are not showing?

Check your cPanel and make sure the database wp_ prefix’s are correctly labeled and has the correct pathing name(s).

This can easily happen with purchased themes or if you started a new host and accidentally altered the mislabeled a database – If your new database prefix’s do not match EXACTLY with your existing media file settings your images will not work.

Likewise, you could have easily missed keyed a 0 (the number) instead of a O (the letter). Ouch!

Step 22: Before proceeding any further please contact your web developer or hosting provider – Sometimes you may have unforeseen issues during WordPress updates that can alter your websites core foundation code and/or table fields. At this point it is easier for a web developer with knowledge of command lines to comb through a website to find strings of code that are broken. If you feel comfortable for the next grind feel free to proceed to the Last Resorts at your own risk.

Step 23:Try re-installing WordPress again, but STOP – Did you backup your website before you thought about re-installing? Make sure to do this first. After re-installing WordPress start importing your themes files and plugins. If these solutions still do not work, feel free to contact us and we will try to help.

Why does this reinstalling WordPress work? Sometimes your downloaded files get corrupted or do not download at all. Normally it is easier to reinstall WordPress than to go through and find the corrupted or missing files.

Be Cautious: Doing some of these steps could potentially open up your website to a security breach, mainly by changing the directories and at step 19 to get your Media Library to function you can try CHMOD 777 in the directory.

The reason people highly suggest to not use 777 as file permissions is that it could potentially create a security breach because the CHMOD 777 means that everybody has access to the folder and can write/read the files. Violators sometimes may take advantage of this. We highly suggest that if you did change the folders to CHMOD 777, to contact your host provider and see if there is any way around this.

Keep in mind that most host servers have your website compiled on a server, with up to 100+ other customer websites. If they had to create any changes to that server for another client, your website will be affected too. If you mention this error to them they should be able to fix this issue or migrate your website to a different server. This will ensure that your new server will contain different site restrictions or security options allowing you to not use CHMOD 777. Feel free to comment if you find any other suggestions that can be taken to solve the WordPress Media Library to work properly.

Last Resort: If you have tried everything you can always reach out to your hosting service to reset your server. With our hosing service they will automatically run backups, but they will charge us if we have to set our site back. Other hosting companies only do this if you pay. This is why you need to run your own backups on your websites. Each host is different, but again this is the very last step where all hope has been lost! YOU WILL LOOSE EVERYTHING, that is after the day your host ran its last backup. I cannot stress this enough, because 99% of the time you will not have to resort to resetting your server back. If your Media Library is still not working there is only one more step that I can fathom.

Last Resort of the Last Resort: Sometimes the best resort is to simply moving hosting and redirect your domain to the new host. Reasons behind this is that many hosting companies split each server up for multiple customers and bandwidth can become spread to thin. It is fairly easy to switch hosts even if you do not have coding experience with the right customer service.

We have found that Bluehost is amazing for transferring websites and they have great pricing. Best of all you get great bandwidth and due to their higher bandwidth it will assist with many of the WordPress Media Library issues you could be having. Best of all you cannot beat their customer service and they will get this issue fixed, even if it is still not working. They are top notch!

Take advantage of this discounted WordPress web hosting starting at $7.99 $3.95/mo. by clicking here.

You will get a FREE domain, FREE site builder, actual 1-click WordPress Installation and 24/7 Support from Bluehost!

Update: This issue also occurs when using WordPress on a MediaTemple dedicated-virtual server. Here is an article we wrote on how to correct this issue on MediaTemple servers.

Update: If none of these steps work and you are using Chrome or IE, try Firefox. This seems to be an issue in IE and Chrome (maybe from these plugins) – Using FF 21 or 22 seemed to work for a few people.

Have any other solutions to “WordPress Media Library Not Working”? Please don’t hesitate to add your solutions in the comments below.

Hope this helps fix your media library!

The post How To Fix WordPress Media Library Not Working appeared first on Ideas and Pixels.

One would think that the answer is obvious: you either have an invalid key or you’ve specified an incorrect referrer. But as with most generalized error messages, neither one is the answer. Google’s policy for their Google Maps API is that they don’t require a token or public key if you’re not using Maps for business purposes (which is only used when you exceed their daily quotas). If you don’t have your credit card details saved in the API console and you try to use a public key for your Javascript Maps call, it returns “invalid key”. Google forgot to tell us this important detail.

To fix this problem, simple remove your key from the API call. Simply using this will do:

<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?v=3&sensor=false"></script>

Yes, it’s that mind-numbingly simple to fix. As is life.

The post Google Maps API – Invalid Key Or Referrer Fix appeared first on Ideas and Pixels.

After doing a bit of research I realized “get_post_meta” does not have the ability to add in paragraph spacing for a custom post type. This is when I found a crafty piece of code call wpautop“.

How To Use WPAUTOP In-place Of Get Post Meta With PHP

Instead of calling out to your description “Get Post Meta” like so:
$description = get_post_meta($your_field_id, 'description', true); echo ( "

");


Replace it with the “WPAUTOP” markup:

echo wpautop(get_field('description'));


Cheers! It is that simple.

The post Get Post Meta Removing Paragraph Tags Fix appeared first on Ideas and Pixels.

{“result”:”failure”,”messages”:”
\n\t\t\t
Country<\/strong> is a required field.<\/li>\n\t\t\t
First Name<\/strong> is a required field.<\/li>\n\t\t\t
Last Name<\/strong> is a required field.<\/li>\n\t\t\t
Address<\/strong> is a required field.<\/li>\n\t\t\t
Town \/ City<\/strong> is a required field.<\/li>\n\t\t\t
Postcode \/ Zip<\/strong> is a required field.<\/li>\n\t\t\t
Email Address<\/strong> is a required field.<\/li>\n\t\t\t
Phone<\/strong> is a required field.<\/li>\n\t\t\t
You must accept our Terms & Conditions.<\/li>\n\t\t\t
Unfortunately we do not ship to to <\/strong>. Please enter an alternative shipping address.<\/li>\n\t\t\t
Invalid shipping method.<\/li>\n\t\t\t
Invalid payment method.<\/li>\n\t<\/ul>”,”refresh”:”false”,”reload”:”false”}

Yes? Fortunately, I was able to figure out how to fix this error quite quickly this morning. The issue has to do with WooCommerce pages. Updating WooCommerce to the latest versions seems to have the occasional effect of deleting some of the required pages. Yet, with the new version of WooCommerce, adding these pages back isn’t as easy as it used to be.

How To Fix WooCommerce Checkout Error

First, go into your database and into the table “options” (or wp_options, if you use the default prefix). Do a search for the option key ‘woocommerce_thanks_page_id’. Once you find it, note the page id that this corresponds with (the value), then go to http://yourwebsite.com/wp-admin/post.php?post=[put the page id from the database table here]&action=edit . If it comes up blank or non-existent, this means you need to create a new thank you page. Create the page (name it whatever you want), then take the new page ID and replace the woocommerce_thanks_page_id with it in the database.

That should do it! This resolved the issue on two different websites for us, so it seems to be a fix-all. Let me know if you have success!

The post WooCommerce Error On Checkout {“result”:”failure”,”messages”:” appeared first on Ideas and Pixels.

The README file states the following: Starting with skrollr 0.6.0 there’s just one thing you need to do: Include an element on your page with the id skrollr-body.

Yes, that’s it. Add id=”skrollr-body” to your body element and scrolling is back.

Thank me later… or in the comments. 🙂

The post Skrollr Can’t Scroll On Mobile Devices appeared first on Ideas and Pixels.

Make Your WordPress Plugin Create Tables

Pay attention to the following working PHP and SQL statement:

// Load global DB object
global $wpdb;

// Create the database table. Change your_table_name to your actual table name
$sql = "CREATE TABLE {$wpdb->prefix}your_table_name (
  referral_id bigint(9) NOT NULL auto_increment,
  order_id bigint(9) NOT NULL,
  user_id bigint(9) NOT NULL,
  date_completed datetime default '0000-00-00 00:00:00' NOT NULL,
  status varchar(24) NOT NULL,
  total_amount varchar(24) NOT NULL,
  disbursed boolean NOT NULL,
  PRIMARY KEY  (referral_id),
  KEY referral_id (referral_id)
);";

require_once(ABSPATH . 'wp-admin/includes/upgrade.php');
dbDelta($sql);

Some things to note here are:

• Every column statement is on its own line.
• I surrounded the $wpdb->prefix portion with curly brackets. This one was big for me.
• I transformed certain commands to lowercase that otherwise might be uppercase, such as ‘auto_increment’.
• There are no apostrophes or quotes around any of the column name declarations.
• Unlike the WordPress.org tutorial, I am using PRIMARY KEY instead of UNIQUE KEY. I am also re-declaring the key below this with KEY key_id (key_id).
• I have two spaces after the PRIMARY KEY declaration.

WordPress’ dbDelta Function Is Tricky, But It May Be Your SQL Statement

One thing I always do is run my SQL statement in phpMyAdmin to see if it works before trying it in the actual plugin activation hook. Often times this will point out that I have malformed commands.

I hope this helps! Good luck and let me know how you do.

The post WordPress Plugin Won’t Create Tables appeared first on Ideas and Pixels.

I mean don’t get me wrong, I really enjoy rainbows, but sometimes even they’re too vibrant and the video below sums everything up!

“Now, what about your online presence? Your designer says “you should use a tasteful color palette”. And you paid them how much? Really get your brand noticed with Florescentsizer!!”

So, how can I disable the Text editor for a User In WordPress?

After a few times of this happening I now use two plugins to stop all of this from happening!

First install TinyMCE Advanced and then the Adminimize plugins.

Open your TinyMCE Advanced settings and set the fields you wish your user to be able to use. Less options seem to work much better or they may try to add in some more flare!

Optional – Copy your websites theme’s styles into the drop down menu, by adding them into your editor-style.css (May need to create this). We tend to skip this step because we hard code the styles into our themes directly and they format automatically.

After this is done, take that user and make them an Editor. By doing this you are stopping 85% of the destruction they maybe able to cause!

Time for the fun! Open up Adminimize and check mark away at all of the stuff you do not want that user to mess with.

Hide WordPress Yoast Plugin From Users and More!

Now if you have been hired as an online marketer, you may want to blog a WordPress User from accessing your Yoast Plugin. You can even other elements in the TinyMCE such as the Title H1 tags and anything else in the dropdowns.

To achieve this, use FireFox or Chrome and right-click and inspect the element you want to hide on the page. Finds its ID as we have and use the image below as a guide to disable the Yoast Plugin from a user.

Did this help your situation out or do you have a better solution? Please let us know by commenting below!

The post Turn Off WordPress HTML Text Editor For Users appeared first on Ideas and Pixels.