Forum Replies Created

Viewing 15 replies - 151 through 165 (of 407 total)
  • @koricoco – Version 5.6.0 has just been released which fixes this issue with topic tags being stripped. Thank you for reporting it!

    Thread Starter codejp3

    (@codejp3)

    Just checked your site again.

    Nav menu link is good.

    Forum Root slug is good.

    Single Forum slug is good.

    Pagination is good.

    No 404 “not found” errors found/

    It appears that you are back to a default bbPress setup. As far as I can tell, you’re good to go.

    Again, sorry for the downtime you experienced. I don’t know exactly what changed on your site, (my guess is something related to permalink/slugs), but that change conflicted with the URL rewriting that my code was performing. We probably could have figured it out and worked through it, but your site would have been dead in the water in the meantime. I still think this non-standard workaround covered in this topic is a viable option for someone that is a experienced with custom code and troubleshooting, but clearly not a good option most site owners. Lesson learned.

    Thread Starter codejp3

    (@codejp3)

    As requested, updated instructions:

    1.) Delete EVERY page you have ever setup related to bbPress forums /wp-admin/edit.php?post_type=page

    NONE of them are needed and they’re only confusing you and conflicting with bbPress permalink slugs. The ONLY EXCEPTION is if you are using LOGIN/LOGOUT pages with the bbPress login form shortcode.

    2.) In your nav menu settings – /wp-admin/nav-menus.php

    Delete the current entry for “Forums” from your menu.

    Add a new “Custom Link” entry.

    Set the URL to:
    /forums/

    Set the link text to:
    Forums

    3.) Go to the WP permalink settings page ( /wp-admin/options-permalink.php ) and click “save” just to force a regeneration of the .htaccess file and cached rewrite rules.

    @sterndata – Thank you for chiming in. I have accessed user sites directly on a few occasions, always as a last resort, never as a shortcut to a resolution. If you read my post above then you will see that I certainly understand the problems with doing this, and the few times that I have actually “touched” a user’s site, I kept their security/privacy/safety as a priority. Nevertheless, I will take your comment to me to heart and limit what I am willing to do in the future. Thank you again for chiming in.

    @koricoco

    I’m not being mean or difficult regarding the username and password. I truly have YOUR best interest in heart. Whatever you want ME to see at that URL, EVERYONE can see. Whatever I can DO at that URL, EVERYONE can DO. Considering this is a development site that is not polished/refined/secured/production-ready, there’s a very good chance of finding broken/exploitable things and that can mean very big problems for you down the road, even after you finish development and make the site live. I don’t want ANY issues for your site, now or in the future, whether it’s related to this plugin or not. As a former Network Cyberwarfare Specialist and a certified Security+ professional / Certified Ethical Hacker, I would HIGHLY advise that you never post any credentials publicly ever again for all of the reasons I’ve shared (and many more). It’s not an insult. It’s a professional recommendation and the best possible advice I could offer you. It’s up to you whether you acknowledge and accept that advice or not.

    As for the issue at hand, I’ve tested it on my test server and I can indeed replicate the issue you mentioned (no credentials for your site were needed).

    I’ve already patched the code and will be publishing a new release with this fix, along with changes/enhancements to the topic “favorite” / “subscribe” links/buttons. It should be released in the near future. I will tag you in this topic when it’s released.

    Thread Starter codejp3

    (@codejp3)

    which tells me something isn’t right and it isn’t completely reverted.

    @cj74

    That’s what I see too.

    Your current forum root is:
    /bbpress-forums/

    Your current “General Forum” subforum root is:
    /forum/main-forum/

    Your current menu item for “Forums” points to:
    /forum/

    A lot of mismatches there, and duplicate content at multiple places that’s adding unnecessary confusion.

    1.) Whatever /forum/ is that your nav menu item points to need to be deleted (probably a page with the forum embed shortcode). That page actually has to be deleted since it’s using a permalink slug that conflicts with a bbPress permalink slug that you actually need to use and shouldn’t be used at all in the first place. Delete it from here /wp-admin/edit.php?post_type=page

    2.) The bbPress forum root slug needs to be changed from “bbpress-forums” to “forums”. Change it in /wp-admin/options-general.php?page=bbpress

    3.) The “Forums” link in your nav menu then either needs to point to the forum root slug ( /forums/ ) if you want it to point to the forum root, or the “General Forum” specific subforum root if you want that to be where it takes your users ( /forum/main-forum/ ). Change it in /wp-admin/nav-menus.php

    4.) After all of those changes, go to the WP permalink settings page ( /wp-admin/options-permalink.php ) and click “save” just to force a regeneration of the .htaccess file and cached rewrite rules.

    Pagniation works great using the PROPER “General Forum” link ( /forum/main-forum/ ), but is broken on the IMPROPER nav menu item link ( /forum/ ). Once you apply these 4 changes, in that order, it should be back to original and working correctly.

    @reedy – I’ve been sidetracked with other work and life events, but I am starting on this today and will have a release with these changes done in the near future. I’ll tag you in this topic when that’s done.

    @koricoco

    First, I’ve submitted this topic so that the WP mods can remove that login information you included. For future reference, that’s a horrible thing to post publicly. I have them and will use them if needed, but in the future, please request a private email address or website support form to provide that kind of information directly to plugin developers instead of posting it publicly for the world to see and use.

    Second – can you clarify the problem?

    “Limit Topic Tags to a list” does exactly that. Any tag NOT in that list is automatically stripped and removed from the topic/reply when submitted. It sounds like it’s working as it’s supposed to. If tags that ARE in that list are being stripped/removed, then it’s not working properly and I’ll gladly look into it.

    Thread Starter codejp3

    (@codejp3)

    @cj74

    Just to be clear, this topic and code additions really have nothing to do with the Style Pack plugin. They simply handled URL rewrites. The only part Style Pack had to do with these changes was related to breadcrumbs, and those are default options that have nothing to do with a site crashing. I just want to be clear for anyone who reads this in the future. If you did indeed experience issues related to this topic, I’m sorry to hear that, but it goes with the territory of venturing outside of defaults and standard practices to accomplish something WP core and bbPress were never designed to do, and Style Pack has no direct connection to that.

    Now as for the issues you’re describing, I’m kinda following you, but not quite.

    Your site has been working fine for 2+ months now, but just recently went down due to 500 code server error?

    Sure that’s always possible, but if the code changes themselves we’re going to do that, they should have done that 2+ months ago when you implemented them. Functional and working URL rewrites don’t just stop working for no reason. SOMETHING else changed on your site, with your configuration/settings, or plugins that caused them to stop working. I don’t know what that is, but perhaps it could be narrowed down and addressed. If you have any interest in trying to demystify what broke, you can email the specific errors you encountered to [email protected] and I’ll see what I can find out without direct access to your site.

    As for the 404 “oops not found” errors, you may have to go to the WP settings page for permalinks and click save even without making any changes just to force a .htaccess regeneration and clearing cached permalinks/rewrite rules.

    Not sure about the issue with only showing 15 out of 115 topics, but my guess it that bbPress counts need to be fixed, or you’re using the embed forum shortcodes and pagination is not being utilized. If so, you should not be using a page with forum shortcodes, you should go back to using the default bbPress forum index. Taking a look at your site now to get an idea.

    Sorry you had issues. Glad you were able to restore without data loss. Without knowing what that change was, there’s very little I could do to work through it. Guess you’ll be going back to defaults and just dealing with the “1 extra unnecessary click” that this whole topic/workaround was intended to resolve. It WAS working, but something changed that broke otherwise functional code.

    @clivesmith – Sorry for the delay. I just sent you an email. We’ll go from there 😉

    Is your local test site accessible?

    If not, would you be willing to migrate a copy to publicly-accessible hosting (my dev server will work if you don’t have a suitable hosting plan)?

    The reason I’m asking is that I want to add var_dump() and wp_die() step-by-step through that whole process to see where it’s actually failing and what info/values are present each of those steps, and don’t want to do it on a live site since it will kill the site and expose raw values.

    @clivesmith – the code in that plugin that deals with moving the uploads from the temp dir to the /hm_bbpui/### (post ID) folder is in /bbp-image-upload.php in the “hm_bbpui_insert_post” function (lines 232-277).

    If you can edit line 252 and remove the “@” symbol in front, it should give you an error as to why it’s failing.

    From this:

    @rename($uploadDir['basedir'].'/hm_bbpui_temp/'.$match, $uploadDir['basedir'].'/hm_bbpui/'.$post->ID.'/'.$match);

    To this:

    rename($uploadDir['basedir'].'/hm_bbpui_temp/'.$match, $uploadDir['basedir'].'/hm_bbpui/'.$post->ID.'/'.$match);

    It may display it inline as a hard/critical error, or it may just show up as an error/warning in your debug log, but the “@” is what’s silencing the error related to that.

    Line 235-236 looks strange to me in a logical sense.

    It’s exiting that function if the the post_type is not a topic AND post_type is not a reply. I would think it should be exiting if the the post_type is not a topic OR post_type is not a reply….. but it seems to be working so I wouldn’t touch that code for now.

    @robin-w – thank you for your testing and input. If Clive wants to pursue this further, we may have some simple questions for you (copy/paste kinda stuff from the Style Pack “Plugin Info” tab).

    @clivesmith – If you do want to pursue this further, I will setup a test site on my server where you can play around with this until it gets resolved without messing with your live site anymore like you have been. Let me know and I’ll get it setup and send you the link and login info.

    Strange.

    Here’s what I see in Firefox (text only):

    Here’s what I see in Chrome (text and visual):

    Here’s what I see in Midori (neither controls):

    I refreshed and tried various topics within each browser just to make sure I was viewing after you made the changes.

    Something wonky going on there…

    My Guests do see the TinyMCE visual editor buttons as soon as I enable the image upload plugin

    @clivesmith

    Are you sure about that? Here’s what I see as a guest on your site:

    Same on my test site.

    in fact that plugin over rides the bbp style plugin because the 9. show editors setting in the Topic/Reply form doesnot change what the visitors/ users see.

    @clivesmith

    I’ve noticed that it does some funky things with the “Text Editor” option in Style Pack, but this only seems to affect admins/logged-in users. Guests see no editor period.

    Just a thought is TinyMCE a part of wordpress core ?

    @clivesmith

    Yes it is, and it is possible that changes have been made to WP core within recent updates. I will try to verify this or get any additional info I can.

Viewing 15 replies - 151 through 165 (of 407 total)