Forum Replies Created

Viewing 15 replies - 1 through 15 (of 98 total)
  • Thread Starter nicole2292

    (@nicole2292)

    Given I had not received a response and I uregently need to remove the duplicates attachment posts I hacked the plugin file and changed all the instances of “publish” to inherit. That worked to find the duplicate attachments, however when I try to delete the selected posts from the list I get a pop up error “Response from the server: Unknown error occurred”

    Nothing is deleted.

    I can see in the code that this is an Ajax error however I have no idea how to fix it.

    Can you please help with using this plugin to delete attachments? Ideally with making it work for attachments without having to hack the plugin code.

    Thread Starter nicole2292

    (@nicole2292)

    Thanks very much for the response.

    Yes I am aware that the BSR is broken for serialized data on v1.4.4, so I was already testing with 1.4.3 prior to posting this.

    I will see how I go with regex but it’s not my strong point.

    Thanks.

    Thank you so much! I have been banging my head against this exact issue for 2 hours! I just rolled back from 1.4.4 to 1.4.3 and it suddenly went from 4 cells found to 1200 cells found which need updating.

    Thanks 🙂

    Thread Starter nicole2292

    (@nicole2292)

    Thanks for your responses, particularly @seank123 for the suggestion to have an attribute which can be set as “Any…” option for a given variation. I had forgotten that was an option so thanks for the reminder. Based on the combinations which do affect price we have about 30 variations. I did not want to create each of these manually for each product. Therefore what I have done as a workaround is to only add those attibutes which affect price initially then I use the automatic create variations functions to create all 30 unique options. Then I go back to attributes again and add all the other attributes to the product (eg. colors) and they are then added as “any option” attributes to the 30 variations I already generated for that product.

    This workaround has solved my problem.

    Thanks very much 🙂

    • This reply was modified 1 year, 8 months ago by nicole2292.
    Thread Starter nicole2292

    (@nicole2292)

    The entire reason we are using HTML instead of PDF is so the flipbooks can be generated automatically from dynamic website content. We have no interest in using a page builder as if we were going to manually build pages then we could do PDF’s. I’m currently evaluating various flipbook scripts to decide which one is best for this project. I don’t understand your suggestions to add js code to handle click event. I understand javascript. I know what a click event is. I just don’t understand the suggestion with relation to this plugin, which is supposed to work out the box for HTML files. Can you please provide the code snippet which would need to be added? Where would this code snippet be added?

    Thanks

    Thread Starter nicole2292

    (@nicole2292)

    Hello? Is there no support for this plugin? Are hyperlinks not supposed to work?

    Please read my extensive previous post on this topic here: https://wordpress.org/support/topic/get_page_by_title-doesnt-work-if-title-has-an-apostrophe-2/

    This issue is a bug with the wordpress core function get_page_by_title() and unfortunately it has never been resolved.

    Nicole

    Thread Starter nicole2292

    (@nicole2292)

    Thanks so much for your speedy reply.

    It appears that table had become corrupted as I dropped it and now everything is working correctly.

    Thanks for your assistance.

    Thread Starter nicole2292

    (@nicole2292)

    Apologies for my delayed response.

    Thanks for taking the time to reply however your reply is rather confusing.

    The front end and backend are one and the same thing. Well they should be. As in the content shown on the front end is supposed to be exactly that which is present in the “post_content” field of the wp_posts table in the WordPress database for that post. If the shortcodes don’t exist then they should be output as text exactly as they are in the database.

    If you are not cleaning the database then how exactly are you cleaning the front end only?

    Are you somehow parsing the content from the database and just hiding any missing shortcodes before showing the content on front end. Well if so then that’s clearly not working either because I can still see some shortcodes when I view the pages on the front end of the website. Also if that is the case then that isn’t really a shortcode “cleaner” is it? It’s more of a shortcode “concealer” or a shortcode “hider”.

    I would greatly appreciated if you could take the time to explain from a technical perspective what exactly the differences are in how the shortcode cleaner works in both the free and the pro version.

    Thanks very much,
    Nicole

    Thread Starter nicole2292

    (@nicole2292)

    No help here for a plugin that just isn’t working?

    Thread Starter nicole2292

    (@nicole2292)

    P.S. I would use the official support channel but it requires registration and account creation and I don’t feel that is necessary to get support. I already have an account here…

    Thread Starter nicole2292

    (@nicole2292)

    So after wasting several hours on this I contacted the client who contacted the host and they were able to fix the issue. Very frustrating when you think you have missed something but really it’s a server issue and you didn’t even have the necessary access to make the changes required.

    For those wondering the nginx rewrite rules had to be changed to allow for subdirectories.

    Thread Starter nicole2292

    (@nicole2292)

    Hi Paulo,

    Thanks for your lengthy reply.

    Yes your understanding that the slug might change is correct. However the post title and the slug are independant of each other so the post titles could remain the same even if the slug format was changed.
    get_page_by_title() should work as long as the post titles are the same regardless of the slug.

    One post is not a child of the other as they are in two different post types. They are not two posts in the same post type which is heirarchical and thus supports parent and child relationships. It would not work to set them up this way as then they would all be in the one post type which does not create the desired functionality.

    Ultimately I’m not looking for a workaround for get_page_by_title(). I know how to achieve that… I could set up a custom field on the B post to enter the post ID of the master A post and create a relationship that way. However that is extra work for each and every post and it should not be necessary to do that at all given there is a function get_page_by_title() which theorhetically does exactly what we need more efficiently… unless there are special characters!

    So how can we just make get_page_by_title() actually work as it should rather than looking for hacky workarounds?

    Thread Starter nicole2292

    (@nicole2292)

    I have resolved my own issue. There was a wayward addition of an old version of jQuery UI in the custom version of the Bones theme which was causing the problems. The problems with the latest bones theme appeared to be caching related as they have also gone away with the change to the custom theme.

    Thread Starter nicole2292

    (@nicole2292)

    Hi Paulo,

    The reason I need to use get_page_by_title() is that this is a highly complex site and there is a need for two different views of essentially the same post content on two different URL’s. This need was covered in an earlier topic I started here: https://wordpress.org/support/topic/multiple-views-of-a-single-post/

    So we have one master post in a custom post type (lets call it A) which has the main post content and all the custom fields and custom meta data required for that post. It is a complex post with a lot of data.

    Then we have a duplicate of that post created via export and import of just the title in a different custom post type (lets call it B). This has the same post title. Then in the single template to display this post we are pulling most of the content from the master post of the same title in post type A using the get_page_by_title() function.

    The end result is two quite different single post views like this:
    ourdomain.com/posttype-A/our-post-title
    ourdomain.com/posttype-B/our-post-title

    I cannot think of another better way to do this. I really just need get_page_by_title() to actually work 🙂

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