On Saturday, 8 October 2022, after a break of almost three years, we meet at the Pomeranian Science and Technology Park Gdynia / Pomeranian Science and Technology Park Gdynia for the seventeenth time for WordUp Trójmiasto.
It is a meeting of enthusiasts and users of #WordPress and #WooCommerce.We will hear eight presentations + networking = It will be kosher!We expect a knowledge-thirsty Tricity audience in such beautiful natural and unique circumstances.

If you would like to soak up the early autumn seaside breeze, rub your back in the sand, collect seashells and while talking about WordPress to the accompaniment of seagulls – book your time today and sign up for the event.
When: 8.10.2022 (Saturday), 15:00-20:00

Where: Pomeranian Science and Technology Park Gdynia, Building III (CN Experyment), cinema room.

Free admission, registration required: https://app.evenea.pl/event/wordup17/

WordUp is a gathering of the WordPress community that takes place all over the world. The meet-ups are dedicated to both creators (developers) and people who use WordPress daily as administrators, bloggers, SEOs or marketers.


  1. Magdalena Paciorek – Block editor in a dedicated theme – a case study of cyberfolks.pl and kei.pl sites
  2. Maciej Kuchnik – Transferring WordPress better – about WP migration between servers.
  3. Tomasz Kołkiewicz – Canonical links and their significance for SEO
  4. Tomasz Palak – How not to get too inspired?
  5. Marcin Andrzejewski – The last mile in content delivery. Text readability in WordPress.
  6. Marcin Krzeminski – Introduction to WP-CLI
  7. Dawid Urbanski – 1.7 million in 45 months without your own product. How to earn better as a WordPress developer?
  8. Maciej Palmowski – Astro + WordPress =
  9. Panel discussion – moderated by Kamil Kawałko
    – Michał Strześniewski (300.codes),
    – Maciek Nowak (Osom),
    – Max Matłoka
  10. Fluid Talks – PIF PAF, Gdynia 10 February 23


Obviously, it is worth sharing not only your success stories but also your failures in order to anticipate the future better.
During the fucked up session, I had a presentation describing a story where the problem arose over time, and whether the fan would scatter the waste was not a question of if but when.
Crackers literally had attacked a website, and as it turned out, no one had a safe copy, and only defaced backups were available.
DevOps often say that we divide people into those who make backups and those who will make backups.
From the summary of my presentation, it seems worth adding another group of people – those who check whether restoring a backup is successful.

Let me share my latest #AMP Accelerated Mobile Pages #WordPress presentation held at WordUp #Trójmiasto meetup.

Just a recap of the main thoughts about AMP:


AMP HTML is HTML with some restrictions for reliable performance.


The AMP JS library ensures the fast rendering of AMP HTML pages.


The Google AMP Cache can be used to serve cached AMP HTML pages.

Allow only asynchronous scripts

Don’t let extension mechanisms block rendering

Minimize style recalculations

Only run GPU-accelerated animations (position, scale, rotation, opacity)

All #CSS must be inline and size-bound 50KB

Keep all third-party JS out of the critical path (except in amp-iframe )

Font triggering must be efficient

We can prioritise resource loading

No !importants



When you need to add  <body class=”parent-SLUGNAME”> class please add the following code to your functions.php file:



function body_class_section($classes) {
global $wpdb, $post;
if (is_page()) {
if ($post->post_parent) {
$parent = end(get_post_ancestors($current_page_id));
} else {
$parent = $post->ID;
$post_data = get_post($parent, ARRAY_A);
$classes[] = ‘parent-‘ . $post_data[‘post_name’];
return $classes;


Below you’ll find me newest presentation of what’s new in WordPress 4.9

To remove comments rss feed link (and clear othe unnecessary options) just add the following to functions.php file of your theme:

remove_action( 'wp_head', 'feed_links' );
remove_action( 'wp_head', 'rsd_link');
remove_action( 'wp_head', 'wlwmanifest_link');
remove_action( 'wp_head', 'index_rel_link');
remove_action( 'wp_head', 'parent_post_rel_link');
remove_action( 'wp_head', 'start_post_rel_link');
remove_action( 'wp_head', 'adjacent_posts_rel_link');
remove_action( 'wp_head', 'wp_generator');