Modifiedcontent
Forum Replies Created
-
Forum: Plugins
In reply to: [sociable] Remove plugin from print versionIs there still no fix for this? I really regret upgrading the Sociable plugin.
The CSS suggestion only works partly when placed like this:
@media print { #print-link { display: none; } } .sociable{ display: none; }That removes the icons from the print, but not the URLs at the bottom.
The Akras14/tannerhelland.com solution works.
Forum: Requests and Feedback
In reply to: Sociable code is messy when printingIs there still no fix for this? I really regret upgrading the Sociable plugin.
Removing Sociable now…
Forum: Plugins
In reply to: Allowing registration with the email as usernameBeau Lebens actually wrote a cool little plugin for this that actually seems to work!!
You still have to enter a username during registration. Activation emails still instruct the new member to log in with that username, where they in fact now have to use their email address.
So you have to make some edits to the forms and email messages, but that’s no problem. The cool thing about this plugin is that it seems to take care of the tricky stuff in an unobstrusive way.
Happy! 🙂
Doing further testing…
Is it possible to add this line from the “plugin”:
remove_filter('template_redirect', 'redirect_canonical');directly to code somewhere? I can’t access wp-admin, so plugins are useless.
Forum: Plugins
In reply to: Allowing registration with the email as usernameAnyone?
Forum: Plugins
In reply to: [Plugin: Register Plus] Awesome pluginDoes Register Plus work for version 2.7? Will there be an update?
What I’m really looking for is a plugin that replaces silly usernames – like ‘viperman324’ etc. – with email addresses, so all members need to log in is their email address + password.
I want to entirely eliminate the concept of “usernames”.
Forum: Plugins
In reply to: Allowing registration with the email as usernameDoes anyone have any ideas?
Forum: Plugins
In reply to: Allowing registration with the email as usernameI’m looking for the same thing. I want to get rid of silly anonymous usernames. I want to let members sign up with just their real full name + email address and send password in the confirmation email. Whereever the username is used as default, I want to show the full real name or the first name.
For sign-up/login: email address = username
For the rest of the site: username = real nameWhat is the least intrusive way to achieve this?
Forum: Fixing WordPress
In reply to: WP export/import strips object code?Apparently it’s an underdocumented peculiarity of WordPress MU.
Forum: Plugins
In reply to: Best Anti Spam Plugin For CommentsHow can I use Akismet on self-hosted WordPress? It requires a WordPress.com API key. Makes no sense.
Is there no good comment spam solution for self-hosted WordPress?
Forum: Fixing WordPress
In reply to: Blog posts on a page outside WordPressquery_posts(‘showposts=5’); doesn’t work anymore in 2.7
What’s the latest way to do this (2.6 officially I guess)?
Forum: Fixing WordPress
In reply to: When was the horrible revisions feature introduced?That’s a hack that only partially solves the problem. For my specific purpose I returned to WP 2.2 and that works fine. WP jumped the shark…
Forum: Plugins
In reply to: Add wp_posts custom fields to editor in version 2.2In this case I use WordPress to manage a table of “records” instead of blog posts. I already had this table with another script, but needed a flexible category system like WP has.
Yes, I went into MySQL to add these fields. I’m not a PHP/SQL coder, but I’m trying to get to the basics, not pile on more WP specific code and plugins.
Again, as far as I can tell the Custom Field option stores data as meta data, not regular fields. That is no good, because I want to be able to access the same “records” table through other scripts.
Even with turning off post revision the latest versions of WordPress don’t seem to keep the integrity of the records. They still create new versions with new IDs.
I also couldn’t get custom permalinks to work in my modified WP 2.6 experiment. In 2.2 it works beautifully. For straightforward blogging WP 2.6+ is fine, for anything else WP has jumped the shark imho.
So no, thanks for your effort, but your post was not helpful at all. I deliberately mentioned these points in my original question, hoping to avoid answers like yours.
So forget all that, here’s my question again:
I have manually added several custom fields in the ‘posts’ table in the database (‘tagline’, ‘url’, ‘address’, etc.). I’m trying to edit edit-form-advanced.php to add form input elements for these fields to the editor page in admin.
Adding the form input elements is not that complicated, getting the input stored is trickier. Where is the code/query that stores the data from the edit-form into the MySQL ‘posts’ table? Which WP files are involved in this process?
Figured it out (I think…). Something like this for posts from categories 3 and 5:
SELECT * FROM posts LEFT JOIN post2cat ON (posts.ID = post2cat.post_id) WHERE (category_id = 3 OR category_id = 5)What would it be for WordPress 2.2?
It has different table names and probably structure. Can’t figure it out. Found this on another thread about changes for 2.3:
$wpdb->categories is replaced by $wpdb->terms
$wpdb->post2cat is replaced by $wpdb->term_relationships
$wpdb->post2cat.post_id is replaced by $wpdb->term_relationships.object_id
$wpdb->post2cat.category_id is replaced by $wpdb->term_relationships.term_taxonomy_id
$wpdb->categories.cat_ID is replaced by $wpdb->terms.term_idwp_terms now contains all the category (read: taxonomy) names and IDs.
wp_term_taxonomy contains the term (read category) ID, a description of what type it is (category, link_category, etc), the description and the number of posts/links in that taxonomy.
wp_term_relationships contains a lookup of an object_id (read: post ID, link ID, etc) and a term taxonomy ID (from the term_taxonomy table, which relates back to the category).
Other refs to look out for are (especially when they are used OUT of the above context):
cat_ID –> term_ID
categories –> terms
cat_name –> nameI get this far:
$query = "SELECT * FROM posts as wpost INNER JOIN post2cat ON (wpost.ID = post2cat.post_id) INNER JOIN term_taxonomy ON (post2cat.category_id = 3) AND term_taxonomy.taxonomy = 'category' AND term_taxonomy.term_id IN (3)";I have no clue what to do with term_taxonomy and probably need a different structure anyway. Can’t puzzle it together.