Steveorevo
Forum Replies Created
-
Forum: Plugins
In reply to: [bbp style pack] FSE footer in 2024 and 2025I’ve isolated the issue in 2024 so far. The most significant changes appear to be a few CSS rules that are failing to be honored in the footer area. Forcing these seems to fix layout issue. I.e. the css rule for .is-content-justification-space-between sets the justify-content: space-between on /sample-page but for /forums this is set to normal in the footer area.
There is still a minor color and line spacing I’m still isolating but placing these rules in one’s style.css (I’m child theming Twenty Twenty Four) seems to correct the issue:.wp-block-group-is-layout-flex {
align-items: flex-start;
}
.is-content-justification-space-between {
justify-content: space-between;
}
.is-content-justification-stretch {
align-items: stretch;
}
.is-vertical {
flex-direction: column;
}I also noticed that the entire footer area is encapsulated by the <footer class=”wp-block-template-part”> that is missing on the forum pages. I tried adding it but it didn’t seem to change rendering. Overall, now that I’ve come up with a CSS differential method, I can easily compensate for these issues. Happy if this contributes to a more permanent resolution; otherwise I think this matter can be closed from my POV.
Thank you!- This reply was modified 4 months ago by Steveorevo. Reason: Update
Forum: Plugins
In reply to: [bbp style pack] FSE footer in 2024 and 2025It is identical in 2024, and 2025, it’s not empty head tags (that’s my debugging introduced issue). I did do a differential between the “/sample-page” and “/forum” and they are mostly identical. However, some style tags appear to be moved from <head> down to below <footer>, i.e. <style id=’wp-block-site-logo-inline-css’>. How this contributes to the footer rendering, I’m not sure. I tried manually moving the styles back to the head in a captured HTML file and it made no difference.
Forum: Plugins
In reply to: [bbp style pack] FSE footer in 2024 and 2025I should add that it appears that the /forums/ pages have empty head tags. Rather, it looks like stylesheets and JavsScript is being injected in the body tags. Likewise, the body tag itself is missing class names found on a typical installations of 2024 and 2025.
Even simpler; add this one line to twenty twenty two’s index.php file; this will preserve the theme’s menus, header, etc. and tell WordPress to use 2022’s template engine:
include ABSPATH . WPINC . '/template-canvas.php';Or, to prevent losing changes when/if 2022 updates; use this hook in your own functions/plugin/child:
add_filter( 'template_include', function( $template ) { if ( false !== strpos($template, 'twentytwentytwo/index.php') ) { $template = ABSPATH . WPINC . '/template-canvas.php'; } return $template; });- This reply was modified 2 years, 10 months ago by Steveorevo.
I found a simple fix; since twenty twenty two doesn’t use PHP template pages anymore, I simply replaced Twenty Twenty Two’s otherwise empty index.php with the “skinny” template index.php I created here:
https://gist.github.com/Steveorevo/96d8015bcf353221e1cf0cd6b89bb766
It’s based on the basic, default, template page as described on WordPress’ Getting Started -> Your First Theme.
Likewise, anyone find any resolutions?
Forum: Reviews
In reply to: [DesktopServer for WordPress] Avoid at all costsI can’t make you read the link, nor follow the directions on how to change it. I guess I should append to that list:
It’s not recommended, but you can.
It’s not convenient, but you can.
It’s not supported, but you can.
* It’s possible for most users except ^^^ this guy (gxpcx)Forum: Reviews
In reply to: [DesktopServer for WordPress] Avoid at all costsHey folks, I’m the creator of DesktopServer so I’d be happy to answer your questions (time allowing). I own the dev.cc (although contrary to belief, you don’t have to use it; even with the software package I created). I registered it and will always ensure it resolves back to 127.0.0.1. Again, you don’t have to use it but it’s there for your convenience.
I pay the annual registration for it. It’s not a “bait and switch”. It will continue to work as a localhost alternative even if you’re a “blame and slander” complainer.
https://wptavern.com/desktopserver-3-8-4-includes-a-gift-to-the-community
It will continue to work even if you’re not a DesktopServer user too. It just resolves to 127.0.0.1. I used to use “.dev” as many folks did, but Chrome changed things so I (and every other dev I know) needed a simple 127.0.0.1 resolution. So why not append two characters? I did. End of story.
However, you can change the TLD in DesktopServer to whatever you want.
It’s not recommended, but you can.
It’s not convenient, but you can.
It’s not supported, but you can.I don’t recommend using .com because [most] mature & professional developers already know that it’s a popular REAL TLD that could cause confusion locally, break plugins, create a security risk, and/or conflict with real & actual, SSL certs. Using a testing TLD is important.
- This reply was modified 6 years, 6 months ago by Steveorevo. Reason: Grammar folks! It's important. :)
Forum: Plugins
In reply to: [DesktopServer for WordPress] Compatibility with WordPress 4?Please ensure you are using the most recent version of DesktopServer (3.6.5). We’ve updated the plugin to version 1.5.0. However, the prior version 1.4.0 is compatible with WordPress 4.1.1.
Also tested on DesktopServer 3.6.2 and Hostgator Reseller accounts. Same behavior. Also noted that deactivation and deletion of the plugin leaves the problem tables behind. This can aggravate backup plugins such as BackWP Up, etc.
Experiencing the same issue. WordPress installs with core tables set to utf_general_ci but yet WordFence creates new tables as latin_swedish_ci.
Enforcing the collation in wp-config.php, yet the setting appears to be ignored. Table creation is still creating tables with latin_swedish_ci.
WordPress 3.9.1 – plain default install from www.remarpro.com on XAMPP.
Forum: Plugins
In reply to: ACF Premium addons (and in general). GPL confusion.Love ACF too, but this simply violates GPL. It cannot prevent or inhibit other GPL code from being distributed. This is a fundamental of GPL. If ACF Options worked with non-GPL code (ie, not WordPress, this would be fine).
If he doesn’t want update services (a more reasonable request, that follows GPL), SaaS does not necessarily apply to GPL and it could be inhibited outside of its distribution by requiring a passcode to access such services. Here, he suggests removing a line of code. That’s not GPL friendly either. Rather, he should make the service portion (furnishing updates in a timely manner) a paid service requiring credentials to function.
Forum: Localhost Installs
In reply to: problem on installing on webmatrixUnfortunately Web Matrix installs II7, compatibility items for PHP under IIS (IIS’ native programming language is ASP -totally unrelated to WordPress, which is written in PHP), Microsoft SQL Server reporting tools (even though WordPress uses MySQL and not Microsoft SQL), Microsoft SQL server (which is no small program) along with a whole plethora of other compenents. Uninstalling all of that is a challenge too. Performance is also abysmal. There are other issues too, as Microsoft’s platform installer servers may not be online, or working correctly.
Microsoft is making progress on this front however, and Windows8 promises to include much WordPress friendly integration. The platform installers might be fixed someday soon too.
Did you want to wait for that to happen or perhaps install a more compliant stack that WordPress was originally developed on and for, such as Apache, MySQL, and the original PHP interpreter? Consider ServerPress.com or InstantWP instead.
Forum: Localhost Installs
In reply to: Installing WordPress locally – don't understand the instructionsHi Sarah,
You might want to try DesktopServer Limited (serverpress.com). It’s free and allows you to create multiple, isolated, wordpress websites in just a few seconds (as it includes wordpress and everything needed to get running right away). This makes it easy to play around on one site (break it even), another to test plugins and themes, and another just for getting work done. Here is a video:Forum: Fixing WordPress
In reply to: Dreamweaver cs5 Live viewYou need to setup Dreamweaver with a site definition. You can use an automated tool to do this for you (premium product, that does more then XAMPP alone):
Using Dreamweaver for WordPress
Or you can follow these (lengthy, but free) directions:
Editing a WordPress theme with Dreamweaver CS5 – Part 1: Learning the basics and Part:2