fireundubh
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: wp_nav_menu getting rid of divIn case anyone is still looking for a way to remove the container and unordered list elements:
$m = wp_nav_menu(array('echo' => '0')); echo strip_tags($m, '<a>');This code stores the menu in the $m variable. The strip_tags() function then removes all HTML tags from the stored menu, except for the links. This effectively eliminates the need for inline styling, at least under specific circumstances.
Use the fix I posted above on add-to-any.php.
Seriously, why does this keep changing with every version? I want the share link to be displayed inline. I don’t want a line break. How do I fix it now?
Edit: I fixed it. Do this:
if ( ! isset($args['html_container_open'])) $args['html_container_open'] = "<div class=\"a2a_kit addtoany_list\">"; if ( ! isset($args['html_container_close'])) $args['html_container_close'] = "</div>";Delete the DIV tags.
I switched from ShareThis to AddToAny because there wasn’t a line break, and then the update added a line break… Thanks for the fix, too.
Forum: Fixing WordPress
In reply to: SQL: Export Comments by Author?Thanks. I’ll try this out.
Forum: Fixing WordPress
In reply to: SQL: Export Comments by Author?Bump.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEPatches should be on this page.
http://ww.wp.xz.cn/download/Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEI’m not understanding your question, whooami. Do you understand this thread? I don’t think downloading a single upgrade file is difficult. I think downloading a single upgrade file that contains unchanged files, including the Kubrick theme, makes upgrading unnecessarily difficult.
By the way, I’m not a new forum user.
http://ww.wp.xz.cn/support/profile/106036Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEand shouting posts like this just get us all going (warranted/needed), right?
Yes, well, I was angry and needed to shout. You’ve all had kneejerk responses in your life, right? Sorry for shouting, but like I said, I stand by my criticism.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEI’m not arguing your point, I just think it’s pretty hard to justify “shouting” at anyone other than yourself. Especially if you knew from past experience that this would happen on the next upgrade as well.
Right. I’m pissed at myself for not remembering to remove the default theme from the upgrade package, and I’m pissed at the lack of better upgrade packages, especially at the frequency WordPress releases upgrades.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMELOL…
Laugh all you want. I’ve designed plenty of unique themes (i.e., themes not based on other themes) and manage at least six different corporate and nonprofit websites that use WordPress as a CMS, not just as a blogging platform. I do things the way I do them for good reasons.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEBut you can not argue with the upgrade instructions…
Instructions are indicative of poor design.
The fact is that the Kubrick theme is included in every package by default. There should be an installation package and separate upgrade packages. The Kubrick theme should only be included in the installation package for first-time users and initial configuration. The Kubrick theme should not be included in upgrade packages in which only a few files of many have actually been updated.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEWow – if you mess with the default theme and don’t save it, you can’t blame the devs, it’s just like changing any other core WordPress file.
I didn’t mess with the default theme. I deleted the default theme and place one of my own themes in a “/default” directory. I’ve ran into problems with past versions where WordPress resets the default theme and breaks the site. Placing your own theme in a “/default” directory ensures that WordPress always uses that theme.
I know – the next release of WordPress shouldn’t update any files, just in-case somebody has made changes to them, wouldn’t want them to lose any changes now would we?
Sarcasm is stupid. My criticism is valid. Your assertion is not.
Forum: Requests and Feedback
In reply to: STOP PACKAGING UPDATES WITH THE DEFAULT THEMEThe first step when you upgrade : make a backup.
The first step when making upgrades available: make individual upgrades available. The open-source community has been doing that for at least a decade. Proper versioning precludes requiring users to re-download untouched files, such as the default theme.
The first step on a forum : do not shout with CAPS…
No, CAPS is “shouting.” And that’s precisely what I was doing.
Nobody have to take the blame for the fact that you’re unable to read the instructions…
Whatever that means. I wasn’t blaming anyone else for destroying my theme. I was blaming the developers for poorly designing the upgrade process which led to my theme’s destruction. I normally remove the default theme from the archive prior to extraction. Your insult was completely unnecessary and unwarranted.
That said, I managed to “recover” the theme that was overwritten by piecing together snippets of code from other unique themes I’ve created. But my criticism of the upgrade process still stands.
Forum: Your WordPress
In reply to: Heretic | WP as Enterprise CMSI’ve been a designer for more than a decade. I can tell you, from my experience, that even the best designers don’t think alike. As for your criticism, it’s purely academic.