Masood Mohamed
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Sydney] Theme Versioning & CachingHi Mahmoud Hossam,
When Sydney releases a new version, they update both the CSS content and the version number in functions.php (if the CSS is updated), so the hard-coded version always reflects the actual file state, this method ensures proper caching and works well.Managing separate versions for each file can feel a bit tedious, but from a technical standpoint, it’s the right approach, stylesheets should only reload when they’ve actually been updated.
Regards,
MasoodHi bjnbdk,
I can help with your Stack block layout, but first could you double-check your WordPress version?
You mentioned WordPress 4.8.2, but the blocks you’re describing (Stack, Cover, Navigation) and Twenty Twenty-Five theme need WordPress 6.7 or newer to work. You can check your version under Dashboard → Updates.
Assuming you’re on 6.8.2,
Select your Stack block and in the right sidebar settings, set “Justify items” to “Space between”. This will push your Navigation to the top and Paragraph to the bottom while making the Stack stretch to fill the Cover block’s full height.
Could you also share your page URL? That way I can take a look and provide more specific guidance if needed.Forum: Themes and Templates
In reply to: [Sydney] Theme Versioning & CachingActually, using a hard-coded version in the parent theme is intentional and the correct approach. By keeping a fixed version, the parent stylesheet isn’t reloaded unnecessarily every time the site loads, which improves caching and performance. The version only needs to change when the parent theme itself is updated, not every time a child theme changes its CSS.
The child theme CSS always loads after the parent CSS, so it will override parent styles as long as the selectors are equal or more specific. If a child theme style seems not to apply, it’s usually due to selector specificity, not the hard-coded version. In that case, the child theme can simply increase selector specificity or use standard overriding methods to ensure its styles take precedence.
In short, the hard-coded version is not a problem, it’s proper caching behavior, and the child theme works correctly on top of it.
Forum: Themes and Templates
In reply to: [Chaplin] PHP version?Hi sallijane,
Yes, you can safely upgrade. I’ve tested the theme with PHP 8.4 and WordPress 6.8.2 (with debug enabled), and it runs smoothly without any errors.
Regards,
MasoodForum: Themes and Templates
In reply to: [Really Simple] Hide the author informationHi flauberthenriques,
Please navigate to Appearance > Customize > Custom CSS, then add the below CSS to hide the author block in single post.
.single-post .post .entry-header span {
display: none;
}Yes, I’ve tested the theme with PHP 8+ and WordPress 6.8.2, and it works without issues. If you notice anything unusual, feel free to update this thread.
Regards,
MasoodForum: Themes and Templates
In reply to: [Neve] Strange string of numbers in top left cornerHi Hagetess,
Thanks for reaching out! I noticed the number is showing only at the top of your homepage, which usually means a theme template or plugin is echoing something into the body.
To track this down, please check your child theme files (like front-page.php, home.php, or header.php) to make sure no stray echo or debug line is present. If you don’t see anything there, try switching to a default theme such as Twenty Twenty-Four and see if the number disappears. You can also disable all plugins and then reactivate them one at a time to identify if a plugin is responsible.
Let me know what you find.Forum: Themes and Templates
In reply to: [Extendable] Wishlist question / issuesHi there!
The plugin you mentioned is outdated and doesn’t support the latest WordPress versions, which is likely contributing to the compatibility issues you’re experiencing.
I’d recommend these alternatives that work well with the Extendable theme:
WPC Smart Compare for WooCommerce(https://wordpress.org/plugins/woo-smart-compare/)
WPC Smart Wishlist for WooCommerce(https://wordpress.org/plugins/woo-smart-wishlist/)I’ve tested both plugins with Extendable and they integrate smoothly. They use modern coding standards that don’t rely on inline JavaScript functions, which is why they avoid the security conflicts you encountered with the previous plugin.
You’ll need some minor CSS adjustments to match your theme’s styling, but the core functionality works without issues. These plugins are actively maintained and compatible with current WordPress versions.