How to get rid of Atom's Welcome screen - atom-editor

I searched around the net and the solutions are too complicated. Is there any easy way to get rid of the "Welcome Guide" Screen?

You have two solutions. I think the second achieves the best when you say "to get rid of":
By unchecking the option Show On Startup in the configuration of the Welcome plugin (Settings » Packages » welcome), Atom doesn't show the Welcome screen at startup (or when opening a new Atom window), but still loads the plugin:
By disabling the Welcome plugin (Settings » Packages » welcome), Atom doesn't load it (which saves memory) and so doesn't show the Welcome screen (under any circumstance):

On OS X, you go to menu Atom → Preferences → Packages and then you have to either find Welcome in the Core Packages or use the filter. You can't get there by going directly to packages in the top nav. Crazy.

I am running Linux Mint and I deselected to "show on startup" and turned off telemetry, but for some reason was never saved and always showed. Even going through preferences did nothing for me to fix the issue. This was the only thing that fixed it for me was creating a config file for it in my home directory under the .atom directory.
cat ~/.atom/config.cson
"*":
core:
telemetryConsent: "no"
welcome:
showOnStartup: false
There are other values for this file, but these should turn off the Welcome screen and Telemetry if it keeps showing up for you.

The easiest way that worked for me is when the welcome page appears, uncheck the Show welcome guide when open. For clarification Here is the image

It sounds pretty trivial, but after disabling the welcome guide from the welcome page,
and restarting Atom you may still see the welcome guide if you didn't close the page and have the "Restore Previous Windows On Start" (under Settings → Core) set to "yes" or "always":
Simply make sure to close the welcome guide before you restart Atom (or if you do not want to have windows restored you can also change that option to "no").

Related

How to fix elementor update causes Server error

When i update my home page using elementor I am getting a server error (503 error). However, my other page updates seems to be fine. Can someone help me find out the root cause? where can i find the logs?
So far i tried,
Clear the cache
Enabled the editor load method in elementors advanced settings.
Deactivated and reactivated the elementor plugin.
***UPDATE: When using developer tools, i get these error upon clicking update.
This link could help explain what's going on:
https://wordpress.org/support/topic/13-feb-update-elementor-error-503/
It recommends trying Elementor safe mode first and foremost.
I would also recommend trying the operation that fails with your developer tools open. Right click on the page, select Inspect (or similar), the tools appear. Click the Network tab and then reload the page and restart the update process that fails. Look at the files being requested
If you see anything that turns red there, or a file that has any other http status code than 200, it may be the error right there. If you click on that file you may be able to get more information about why it doesn't load. Try the headers or response tabs in the panel that opens up.
Where your server logs are located depends on your website hosting service. Read on their pages where to locate them or get in touch with their customer service. Try to post the relevant part of the log here if you see something out of the ordinary.
just add a single line in wp-config.php
define('WP_MEMORY_LIMIT','2048M');

Unable to edit my Wordpress website (through MAMP)

I downloaded MAMP and Wordpress and started creating my website. Later, when I tried to access my website to edit it, I found I could only view it and but don't know to get to the page where I can edit it.
I open MAMP and click 'Open WebStart page' and it opens the start up page. Originally, I thought I was able to click 'My Website' at the top and it would take me to a page where I could edit it. Now it just takes me to a preview of the actual website.
I finally decided to just create a new WordPress page but when I watched a tutorial, I noticed the person clicked 'phpMyAdmin'. I don't have that as an option, my menu says 'Start, My Website, phpInfo, Tools, FAQ, Mamp Website.' So I'm very confused and can't even figure out how to start over. Any help would really be appreciated. Thank you!
As far as accessing phpMyAdmin you may have to go into your MAMP preferences, select PHP and then select 7.0 PHP version that will initialize the phpMyAdmin link. However that does not solve the dashboard problem.

I have no php versions to choose from in drop down cpXstack

After installing cpXstack I want to activate nginx on one of the domains. When I open the cpXstack icon in cPanel, I have an empty drop down, where I should have several PHP versions to choose from.
So I'm stuck and don't know what to do now.
I wonder if anybody knows how to solve this.
Thanks,
Maurice
Today I'm trying to install cpXstack as well, I don't think you need to see the dropdown there, I noticed in /opt/pifpm/scripts the possibility to choose the php version by:
toggle_phpfpm.sh username 5.5.14 1
however for me it's still not working, still debugging

WooCommerce breaking Wordpress Admin

I've made a clean install of Wordpress on my server and added WooCommerce plugin. Now, some of the pages in the admin panel doesn't display correctly (Dashboard, Media, WooCommerce, etc.).
This is a clean install, only WooCommerce plugin is active.
Do you have any idea why this is happening?
Thanks
Ok so there is VERY little information to go on here so here is the general "Wordpress Broke" debugging guide.
Disable WooCommerce and see if Wordpress goes back to normal. If this is the case then you have to Reinstall WooCommerce. This is where http://docs.woothemes.com/document/known-conflicts would come in handy
If it is still broken without any plugins then you have to check your directory permissions, file structure, and URL Structure.
99% of the time chrome devtools will be your best friend for debuging these problems. It looks like you are not loading some of the core CSS files so lets look to see if you have a a 404, 403, or 500 error when chrome requests them.
Open up chrome and go to the Wordpress admin
Right click anywhere on the page and "Inspect Element"
Look for the red error icon on the right side (top/bottom) and click it to expend the console.
You will probably see the failed requests in there. Make sure the requests are for the correct urls, such as: http://yourdomain.com/wp-admin/load-styles.php or http://yourdomain.com/wp-includes/js/thickbox/thickbox.css
If that are valid URLs and you have verified that the files exist on the server then you have to check directory permissions: http://codex.wordpress.org/Changing_File_Permissions
Best wishes, let me know how it goes
I have seen that problem quite a while right now. You can try adding a specialized theme that has WooCommerce support like BootFrame Core theme. Or any other themes supporting WooCommerce -> https://wordpress.org/themes/search/woocommerce/ . Once, I used a WooCommerce, installed the plugin before changing any theme and had to create a new DB because the one I made before got corrupted due to the theme not working with WooCommerce. It's just a rare case but it can happen.

Wordpress admin unresponsive in local dev environment

My local dev environment consists of MAMP, Chrome and Firefox. In certain places in the admin any of my wordpress installs are unreponsive, even with a completely fresh install with no plugins or themes enabled.
What I mean is that once I click a button like "save menu" under appearance->menus, or when I for example try to add three pages to a menu, an request is fired without response. One is an ajax request (the add to Menu Button that is) and another one is just a normal post request (save menu), both actions lead to no response.
I tried to
Upgrade MAMP
INcrease my memory_limit in php.ini
And I of course also searched the Internet like crazy for somebody who had a similar problem, to no avail.
Anybody having/had a similar issue?
Turned out this had to do with too much messing around with packages on OSX and nothing with php apache or wordpress for that matter. It behaved quite strangely.

Resources