Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Not sure if it helps but I corrected this by editing the plugin CSS directly. Manually overriding the default color. However, in my case I only experienced the issue with chrome.

    Thread Starter placidsolace

    (@placidsolace)

    Just filled out the contact form, titled with the short description of “Poetica Jetpack Issue”. Looking forward to getting it worked out, thank you very much for the help.

    Thread Starter placidsolace

    (@placidsolace)

    That does it! Thanks @brook for following up and guiding me appropriately. ??

    Thread Starter placidsolace

    (@placidsolace)

    I kinda figured it might be the case. No worries though, I appreciate the help none the less. Aside from where the other thread goes, as I had additional questions there, I will investigate the themers guide further. Thanks again for the help. XD

    Thread Starter placidsolace

    (@placidsolace)

    Okay I think I found the line your speaking of but this is what it shows:

    <?php echo tribe_event_featured_image( $event_id, 'full', false ); ?>

    Being the line of code differs from what you thought it was how should I proceed? I was going to change it to full so it always used the original image, but that’s already there. Could the “false” part throw things off? Also I don’t recall this file ever being edited.

    Thread Starter placidsolace

    (@placidsolace)

    Sadly that does not address the question. It does make the images not blurry because it makes the resized image load in it’s auto resized resolution. The key question is we do not understand why the featured image is being auto resized at random. If you look at some of the other events on the feed there are ones that are loading the actual featured image for the event that we chose where as the ones that we are concerned with are loading some “filename-300×44.png” rather than the chosen “filename.png”. Hopefully that clarifies the question.

    Any chance you can provide a link that does not require a login? Or some advice on how to get a login? I am using the free version, you’d think if it’s a conflict with caching that the information to correct that would be made available to free users as well. Course maybe I’m missing something here, so if that’s the case please just correct me.

    Something’s amiss indeed. Used to have the export function a few updates back. I’ve read that the plugin author sometimes gets little things wrong both in the code and with the plugin update repository stuff, or whatever its called. I imagine in some soon to be released update it will be fixed. Personally, I love this plugin.

    The method I mentioned above works really well for now. The other posts mention some code fixes to the php files of plugin but the most recent version of the plugin appears to be completely different code in the files specified to edit.

    Np, if you are not familiar with the steps, then proceed with caution. Messing things up in phpMyAdmin can break just about everything if not done correctly. If you run into any questions just reply here, I’ll help if I can.

    ~placidsolace~

    Hi oceanazul,

    I literally just went through this, kind of. There are some old support posts out there that were of no use to me, here are the links to what I found if you want to take a look:

    https://www.ads-software.com/support/topic/plugin-redirection-export-redirects?replies=6
    https://www.ads-software.com/support/topic/plugin-redirection-unable-to-export-csv?replies=30
    https://www.ads-software.com/support/topic/how-to-export-redirects?replies=11

    In the end I found the most direct and simple solution was to export the ‘wp_redirection_items’ table from phpMyAdmin in your cPanel and then importing it to the hosting for the new domain. In my case I was not changing domains, just hosts. The other hiccup in my experience was I had to drop the existing table of ‘wp_redirection_items’ and then rename the imported one to that name. The table on my old host was ‘wp_ersn_redirection_items’, for some reason, and removing the ‘ersn’ made everything sync right up. Hope that helps! XD

    ~placidsolace~

    I also am having the same issue. In my case we are using a shortcode that builds the form within the wordpress page editor and then either through AJAX or Javascript converts it too HTML for viewing, obviously, but it seems that the LeadIn plugin looks for the form class before it has been processed to HTML… ? Not sure. It’s been eating away at me and I have been banging my head against the wall trying to fix it. This is where I have gotten thus far, hopefully it helps so both Pixel Pudding and I can get this working for all forms! XD

    ~placidsolace

    Anyone?

    placidsolace

    (@placidsolace)

    @f.junaid right here with you my friend, this is a major issue that needs to be resolved. One idea to make it easier for the plugin developer, could you allow for a “custom field” from the page/post editor to override this? I found a very close solution here but it adds a second canonical URL instead of replacing the SEO Ultimate one. Any ideas on how one could make this work with the plugin? Sadly if this isn’t resolved soon I will be forced to go to another plugin and that not only would be a lot of unneeded work but I also love SEO Ultimate. ?? Thank you in advance for you assistance.

    ~Placidsolace

    Hey Vincent,

    Thanks for the quick response. In the meantime I took the time of looking at the plugin themes CSS code a little closer. It is the CSS code that specifically mentions the class of “container” that is commonly found in other themes that causes the conflict. I did not dive super deep into this to see what styling was conflicting with what, but I noticed that once I changed the plugin’s class to “ca-container” the content section’s width shortened and began displaying correctly.

    So for those of you looking for a quick fix, try changing the CSS within the plugin files. You will not see this in the plugin editor of WordPress, you will have to look at the directory level on your web host. For Vincent, I’d recommend changing this CCS class name to limit conflicts and hopefully for you, a wider adoption of your plugin though you most likely do not need any help in that area, it is a great plugin. ??

    ~Placidsolace

    Just jumping in real quick on this, Vincent, question. What in your plugin could be causing this “full width” thing? It seems as though your plugin is a great, simple, quick solution for a customer area but this not only affects having a sidebar but also affects other areas of our site. I have a staging/test server where I test everything out first and would like to use your plugin at first glance. However the fact that the v4 styling, which looks nicest :D, is the cause of the problem. The basic styling, does not cause the sidebar to push down the page but the menu is just a list. If you can direct me on how I could edit some of the styling I’d be happy to look at fixes on our end as well. I did not see styling for the themes in the PHP file on first glance, perhaps I just wasn’t looking close enough. :/

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