Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Thread Starter ggsmith

    (@ggsmith)

    I have taken a clean copy of the latest version (wp3.9) added nothing to it and kept the 2013 theme active and the included plugins inactive. I pointed it to my website wp-database and confirmed that it is not possible to list comments in desc order: the most recent first. {“first page displayed by default” and “newer comments at the top of each page”} – broken up into pages, with the newest comments showing up first and the oldest last.

    Example: if there are 22 (top level?) comments on a post with 10 per page, the last page should have the 2 oldest comments at the end – but it does not – it has the first 2 newest!.
    Find a post with a small number of left over comments on the last page of comments and see the problem.

    Whatever you want-choose for the number of comments per page, you can’t get it with the most recent comments up front – you will get left-overs. … telling wp to display the last page first.

    The code should be there to “select” and display comments in either order, desc or asc, and start with a full page either way, using options in settings >> discussion, but it is not currently possible.

    Thread Starter ggsmith

    (@ggsmith)

    note that the first page is always the oldest comments and
    last page is always the newest comments and
    newer vs. older only changes the order within that first or last page … etc.

    Thread Starter ggsmith

    (@ggsmith)

    example: If I have 23 comments on a post, (no nesting) and set 10 comments per page, “last page displayed by default” and “newer comments at the top of each page”.
    I get 3, 10, and 10.
    if I change newer to “older comments at the top of each page”. it changes the order of the last 3, but it is still only the last 3 of the most recent comments.
    if I change last to “first page displayed by default” then I get the oldest comments, not the newest. Again, choosing older or “newer comments at the top of each page”
    only changes the order of the 10 oldest comments. either way they are the 10 oldest comments.

    Thread Starter ggsmith

    (@ggsmith)

    how many comments did you have set for each page and how many showed up on the first page vs. the last page?

    Thread Starter ggsmith

    (@ggsmith)

    Yes. I apologize. The default theme that comes with WP is TwentyTen and is the one that did not have errors. It is good.
    I meant to say “even 2010-weaver!” (ver.1.1.7), which is a clone of TwentyTen. There are “Undefined index:” errors on every tab of the admin – theme – options page(s).
    If a person does not go to their wp-config.php file and set debug=true, verify that the code is at least, not sloppy, and then turn it back to “false” after they have checked, then they have just increased their level of risk. Setting debug=off does not “fix” anything. It only hides it.

    The other themes I tried are Arras Theme 1.4.3.1, Calotropis 1.2.7, and Atahualpa 3.4.9 (the worst). With all but Arras theme, there were errors showing up all over the theme’s options pages in admin – as well as at the moment of activating Arras and Atahualpa. (Among other things, Arras is using a depreciated function; Atahualpa and Calotropis are using undefined variables. Not good.)

    Maybe WordPress could raise the level of professionalism by some approval rating for those who “pass debug”. WP itself certainly passes.

    Thread Starter ggsmith

    (@ggsmith)

    Gee. I found where lynnhatzius had the same problem (+/-) about 10 days ago. He logged out but the comment still showed up because he had used the same email address before.
    I was logged out but used an email address I had used before – on a previous comment, moments before. Also, he was told “Only the person who left the comment can read it. It’s a reassurance that their comment did indeed “take” and is awaiting moderation by the Admin of the blog.”
    None of this is mentioned in the comment moderation, DOCS section. That would help.

    I tried it again (from a proxy site), entering a different email, and I saw “held for moderation” with my comment displayed under it, but from anywhere else, it was invisible. Only when I logged in, could I see it, in the “pending” list where it should be. Ah! Finally! “Now I get it”.

    To re-state my question “how is it done?”; It would appear that the “if” logic is in the apply_filters() function, … or more specifically, the call_user_func_array() – from within the apply_filters() function.

    At least, now I understand the logic.
    Thanks.

    Thread Starter ggsmith

    (@ggsmith)

    In all cases, I was logged out. totally. Still, how is that possible since that would require an
    if ( $user_ID ) or …
    which is not there either. there are no conditions at all.

    I sure would like to know how that might be possible.

    thanks,

    As you say, there is about 1/2 meg (more or less) of “_transient_feed_” (aka magpie) data in the options table of the wordpress database.

    I am sure there is a good reason for storing so much text in the options table (or in a cache, or where-ever), but its purpose seems to boil down to a few paragraphs in the Dashboard, displaying popular wordpress plugins, wordpress news, and the wordpress development blog (and my most recent incomming links). For me, the incoming links is nice, but there could be an option to, instead, simply have links to the appropriate areas of the wordpress website for the rest. When we want to see wordpress plugins, news, the dev. blog, etc., we can just go there.

    For now, I know one solution is to comment out lines 49,50,73, and 85 of the wp-admin/includes/dashboard.php file (in ver. 2.9 anyway),
    which stops the fetching of the data, the storing of it, and the display of it on the admin’s Dashboard page, but I admit I like seeing the ‘incoming links’ (line 46) which are actually unique to my site, as opposed to the wordpress links which are not.

    I would not mind as much if the data was strictly ascii, but it is not.
    So, my question is, for line 46 [“wp_add_dashboard_widget( ‘dashboard_incoming_links’, …”] Is there a way to filter the non-ascii information to restrict it (or to convert it to utf8? – but that seems to be problematic as of yet. – I have even had troubles getting my database fully defined as utf8 — because of the non ascii data in the _transient_ records of course)

    footnote:
    lines 46,49,50,73,85 of the wp-admin/includes/dashboard.php file
    commented out with an #:
    46 #wp_add_dashboard_widget( ‘dashboard_incoming_links’, …
    49 #if ( current_user_can( ‘activate_plugins’ ) ) …
    50 #wp_add_dashboard_widget( ‘dashboard_plugins’, __(‘Plugins’) …
    73 #wp_add_dashboard_widget( ‘dashboard_primary’, $widget_options …
    85 #wp_add_dashboard_widget( ‘dashboard_secondary’, $widget_options …

    it is dozens of copies of the same “tell me something I don’t already know” stuff. I don’t want it cluttering up my database, my cache, or anything else. Please!

    It should be noted that the issue is not really relative vs. absolute url’s but only keeping hundreds to thousands of hard coded (and outdated/misdirected) copies of them out of the database. For static web sites, the html “base url=” tag serves that very purpose, to accomplish absolute addressing while eliminating the problem of maintaining multiple copies of a constant string (and canonicalization), as does “define(‘WP_SITEURL’, “. In fact, WP_SITEURL (copied into the variable $siteurl) is being used in wp-includes/functions.php already to build the full (absolute) address to an image from the given relative address. The value of WP_SITEURL is in the wp-config.php file – and has been for a long time. It is time for us to start using it.

    Actually, all images can be accessed with relative url’s. The images that come with the wp install are accessed with relative url’s – to wp-includes/images and to wp-admin/images. Even tinymce, wp-includes/js/tinymce/plugins/wpeditimage/css/, accesses admin images with a relative “url(../../../../../../wp-admin/images/…)”.
    One of the wp forum moderators has said “I’ve seen some discussion about storing images in a relative fashion but don’t know how far that has progressed.”

    Personally, on my wp site, I removed the root portion of all the absolute addresses in both tables (a global search and replace in my editor) and everything, all my images and links, now work fine (and I have hundreds).

    There is a plug-in “search-and-replace” which can be helpful to those sites where they build, edit, and/or maintain their site from behind a firewall or from a ‘development” installation, perhaps a desktop installation (Javier?). That is not a solution, but it might help to fix all the links and images that are not working right now – if you have no other way of removing the erroneous paths. Using absolute addresses within a website is “generally frowned upon” for good reason. It assumes the site will never move, the website name will never change and, there is never a backup or development site. None of those assumptions are valid. Something does need to be done.

    all the absolute addresses in the 2 database tables, wp_postmeta and wp_posts wreck wordpress’s portability.

    On my wp site, I removed the root portion of all the absolute addresses in both tables (a global search and replace in my editor) and everything, all my images and links, now work fine (and I have hundreds).

    Yes, now the issue is how to keep them out. I now upload images with my ftp program, not wp and then spell out only the relative path to the image in the add/edit a post/page textarea.

    consider how wp_includes/images works.

    I apologize. I have been very hard on you.

    You have removed the index.html, and used wp-admin/css/login.css to display your images. If you have not changed code in index.php or, undone your changes, your site should come up (and removed any other changes to (1 or 2?) other files/programs? – if you are not sure, unzip wordpress again and copy up the 1 or 2 originals files to be sure).
    If you want to keep everyone out of the admin area (except you), I think there is a plugin for that. If you want to require that everyone login before they can even see the site, I think a line of code can be written (if not logged in, display the login page) if there is no plugin for it (I have not seen one yet…).

    PS I was not hard on you, I just told the truth: You don’t, little girl. You talk like you know what you are doing but, you don’t. “your parents know what youre doing?”

    It does look like you finally followed directions and put your images in the wp-admin/css/login.css, good, and dropped your index.html which blocked the index.php which is your website (index.php?…etc aka ?…etc) your last comment shows that you still don’t understand that. now, put the original index.php back. and undo what ever else you changed. Then, ask again just what it is that you want to change in the way that wp works. There might even be a plug-in for it.

    the wp blog is index.php the login page is wp-login.php
    you now have 2 login pages and no website. Right?

    I looked at the one of your 2 login pages

    the one at http://www.sendspace.com/file/wuhcio
    and, i saw:
    <input type=”hidden” name=”redirect_to” value=”http://www.youarethescene.net/wp-admin/&#8221; />
    which answers another of your questions

Viewing 15 replies - 1 through 15 (of 25 total)