WordPress 4.4’te Neler Geliyor (Özellikler ve Ekran Görüntüleri)

26 yorumBir Cevap Bırakın

1. Syed Balkhi says

   Eyl 6, 2024 2:24 pm'de

   Hey WPBeginner readers,
   Did you know you can win exciting prizes by commenting on WPBeginner?
   Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
   You can get more details about the contest from here.
   Start sharing your thoughts below to stand a chance to win!

2. ted nixon says

   Oca 6, 2016 2:21 pm'de

   Would desperately like to see WordPress add the ability to copy a previous post. This would make my life sooo much easier.

   TN

   Yanıtla

3. Roland Success says

   Ara 12, 2015 7:50 am'de

   How can I add featured image to WordPress 4.4 on android. Can’t seem to find the icon.

   Yanıtla

4. hannah says

   Ara 9, 2015 12:31 am'de

   Even I update to the version wp4.4, still I am having HTTP error when uploading a image. Please assist me! Thanks in advance

   Yanıtla

   • Luke says

     Ara 9, 2015 11:07 pm'de

     Well if it didn’t work before, upgrading to 4.4 would not likely fix upload permissions.

     Yanıtla

5. Mohammad Tahir says

   Ara 7, 2015 9:39 am'de

   I love new twenty sixteen and fully responsive navigation menu, it works great specially multilevel drop down menus. But i didn’t like a lot of padding and margin around header, I have created a twenty sixteen child theme but i will have to wait WordPress version 4.4. I can’t use it right now.

   Yanıtla

6. Rick says

   Ara 5, 2015 12:08 pm'de

   Possibly a bit off topic but it would be great if WP could include a lightbox style image view as standard without having to resort to plugins to do it.

   Yanıtla

7. Digitalfront says

   Kas 7, 2015 10:45 pm'de

   Speaking of media in WP, I wonder if there will ever come a day that the media manager will be made so that you can organise images into folders?

   Yanıtla

   • Gavin says

     Kas 8, 2015 6:38 pm'de

     I agree! That is so past due!!! When are they every going to add this much needed feature!?!

     Yanıtla

   • Jesse says

     Kas 11, 2015 12:55 pm'de

     There’s actually a plugin which let’s you ‘categorise’ media : Enhanced Media Library.

     There are others which let you create subdirectories and stuff, but this seemed like the easiest, most sensible way to achieve some sort of organisation.

     Yanıtla

8. jim says

   Kas 7, 2015 10:41 pm'de

   In other words, more bloatware to support cell phones and higher res “pretty pictures”. Sigh.

   Yanıtla

   • Shane Hudson says

     Kas 12, 2015 8:29 pm'de

     Quite the opposite really. Currently phones download massive files, this allows phones to download far smaller files. So while it may be a tiny bit more code, it will save user’s a lot of bandwidth.

     Yanıtla

   • Luke says

     Kas 27, 2015 6:56 pm'de

     Are you kidding? If you look at the code the “bloat” should be one query per post to get the images’ metadata, and then it can output the srcset for specific images at specific resolutions, thus saving users time (and money) when downloading from blogs with images.

     If themes do this correctly hopefully 2+mb images downloading for even a tiny image that is “full resolution” will be a thing of the past.

     Yanıtla

9. Joel says

   Kas 7, 2015 2:17 pm'de

   These are great changes, especially serving smaller images responsively and automagically.

   However, I think there is an increasing need for a toggle on the admin side between “advanced”/normal admin area versus a simplified interface which would satisfy most common demands for most users (beyond limiting user permissions). Awaiting that development, which I hope is in the works.

   Why? We just completed a massive, state-wide project to offer WordPress websites to all small businesses, absolutely free, over a two year period. It was supported at the federal, state, and local levels. Free helps with setup, free configuration for most users, free personal support, free this, free that, free, free.

   And basically, it was a massive failure.

   Why? Primarily, due to the “overwhelming complexity” of WordPress, as far as the vast majority of small business owners go. The complexity led to what they saw as a steep learning curve, and huge amounts of time wasted (again, as they saw it).

   So, we simplified the admin side via plugins; still a no-go. Things are getting worse with the added flexibilities/complexities of 12+ pages of theme-options and/or plugin-settings areas.

   WordPress grew primarily because it was simple to use. It has completely lost that simplicity. How simple should it become? Facebook simple. Twitter simple. THAT simple. (Step 1: Throw out the difference between capital-P Pages and posts, argh.).

   Right now, WordPress needs to simplify further or become what it was designed to avoid.

   Yanıtla

   • Steve Covello says

     Kas 9, 2015 9:35 am'de

     I’m sympathetic to the problem your statewide program encountered (as a WP developer for small businesses). However, several clues emerge in your post that show some pretty naive administrative assumptions. Clearly, there was no pilot test implemented that would have informed the program directors that this would be a problem before it was released statewide. DUH! Any WP developer knows that most “newbs” cannot make any use of the full menu options. Second, it appears that there was no calculation of the administrative time needed for follow-up and upkeep.

     WP will never be Fb easy. It is a platform — not an application. To use WP well, the user must apply him or herself to understanding it as tool for promoting a certain goal (marketing, self-promotion, e-commerce, whatever). If you buy a computer, you have to learn how to use it. If you “buy” a free website, you have to learn how to use it.

     Blaming WordPress for not being Facebook is like blaming a cat for not being a dog.

     Yanıtla

   • Mark Kaplun says

     Kas 11, 2015 3:06 am'de

     This sounds like a badly specified project with not enough budget because “everything wordpress is free”. Every seasoned wordpress developer should know that simplifying the admin for the end user is the most important part of the development, and for that you need to know what are the actual “must have” needs instead of giving 1000 options.

     Yanıtla

10. Preston says

    Kas 7, 2015 11:08 am'de

    What changes will the new srcset feature require for theme developers?

    Yanıtla

    • Luke says

      Kas 27, 2015 7:06 pm'de

      Looks like the main thing is to make sure you provide a ‘wp_calculate_image_sizes’ filter for the image sizes attribute, like the wp 2016 theme does:

      Yanıtla

11. Martin Fuller says

    Kas 6, 2015 6:29 pm'de

    Hmmm. One of the things which the literature tells us to do is to to optimise the images for the web including a resolution of 72 dpi.

    The change in WordPress suggests that higher resolution images will be shown at the higher resolution level depending on the viewers screen.

    Many of us will be aware of the Retina Ready approach which I have avoided for a variety of reasons including an increase in technical complications.

    The question in my mind is what resolution should we now use for our images. If you use double the dpi i.e. 144 dpi the loading time is the square of the increase i.e. it takes 4 times as long to load. The maths is 72 x 72 = 5,184 but 144 x 144 = 20,736

    The question in my mind is what and how will WordPress 4.4 deal with this issue?

    Any thoughts?

    Yanıtla

    • Michael says

      Kas 7, 2015 2:20 pm'de

      DPI (or more technically, PPI—pixels per inch) has long been an abstraction for web development. It has been a decade or more since 72 ppi represented a reasonable average. The standard Apple displays have been 100 ppi for decades, and the new Retina is now around 200 ppi.

      On top of that, it doesn’t really matter what you set the DPI/PPI setting to. What really matters is the actual number of pixels in the image, or what you specify as the image width and height in the HTML. You could make your images 2 dpi or 2000 dpi, and if the pixel width and height were still 1600 x 900 pixels, and/or if the HTML display setting was 1600 x 900, it would appear identical to the same image at 72 dpi.

      Yanıtla

      • Michael says

        Kas 7, 2015 2:25 pm'de

        *Footnote: I had to double-check, and it appears the original Apple Cinema Displays were released in 1999, so I shouldn’t have said “decades”. “Fifteen years or so” would have been more accurate.

        Yanıtla

12. Tom says

    Kas 6, 2015 11:46 am'de

    Nice recap, thanks for sharing. A great post worth thinking about would be examples of how to us the WordPress API. I have been searching online for some tutorial and no one has really be example to explain it well, how to use it, examples of usage, etc. Just an idea

    Yanıtla

    • WPBeginner Support says

      Kas 6, 2015 2:12 pm'de

      Thanks for your feedback. We will try to cover it soon.

      Yanıtla

      Yönetici

    • Dave Warfel says

      Ara 1, 2015 11:55 pm'de

      Tom,

      A few resources you might want to explore…

      Jack Lenox has a 50-minute tutorial on building themes with the API.

      Also, CSS-Tricks has a simple example of how to fetch posts.

      Yanıtla

13. Marcus Fant says

    Kas 6, 2015 11:36 am'de

    For the responsive images, does that provide an opportunity to lighten the load and get rid of some plugins that do the same, now that it will be built into WordPress?

    Yanıtla

    • WPBeginner Support says

      Kas 6, 2015 2:14 pm'de

      Yes it will. If you were using a plugin solely for the purpose of responsive images, then you will not need it. However, many plugins offer other features too like lightbox popups, modals, responsive image slideshows, and so on. You will have to evaluate and then make a decision.

      Yanıtla

      Yönetici