goodyis

I’ve tried now multiple times to contact you all via your contact page.
Each time it says “We were unable to process your form, please try again.”
—-
I’ve since confirmed that my hosting has whitelisted the domain.
Still wasn’t working.
—
Your recent update, did nothing to resolve this; except change the error message from the JSON output of the failure to a text response indicating to contact hosting…
—
I’d like to help you debug this.

As your theme was purchased for the added advantage of this block library – the plugin in question. Not having this plugin; I’m not sure the purchase is justified.

So adding the following didn’t do anything:
order allow,deny
allow from all
allow from 45.63.38.87
allow from 45.63.38.87
allow from 45.63.38.87

Hosting provider is refusing to whitelist the domain.

Is there a free whitelisting program that you would suggest that is compatible with your plugin?

Our how would I go about whitelisting that domain via .htaccess file without disrupting other things?

Also happens with [acceptance] fields with/without *required
[select* “option001” “option002” “option003”]
Then condition for different group to show according to option.
– if each group has an [acceptance]

The ‘SEND/SUBMIT’ btn is disabled until all each every acceptance box is marked.

Solution: don’t put acceptance box inside group

If this is a direct function of contact form 7; I am missing something entirely.

Because it appears to me to not be readily do-able ‘out-of-the-box’
– meaning I will have to somehow group a few fields together and use jQuery to add/subtract them

example of jQuery manipulation here: https://tristandenyer.com/using-jquery-to-duplicate-a-section-of-a-form-maintaining-accessibility/

You could try linking them. IF YOU DON’T have tons and tons of orders being placed at the same time.

https://www.skyverge.com/blog/automatically-link-woocommerce-orders-customer-registration/

It has been a month.
Still have not heard from you guys after sending in an email 3 weeks ago with details.

I’ve updated each time, and still hangs; badly.

I have uninstalled for the most part and just manually added tracking back in.
= no dashboard (what I did like about your plugin)
= no more hanging (what I couldn’t intentionally allow)

If I don’t delete it from other stage installs; I might see if I can’t get it to work again… but maybe not.
– I’ve seen too many other comments about what they called ‘malicious injections;’ now, I would not go as far as malicious by any stretch, but something for sure is not ‘kosher.’

• This reply was modified 7 years, 8 months ago by goodyis. Reason: Not truly resolved, but resolved in the sense that I've moved on

@chiknii You end up getting this working?

So… I got it to work on the stage environment.
I first got it working in the same fashion that your plugin had it working; just inserting a fallback image for those posts that didn’t have a featured image; but – like your plugin – it only worked on the first page.

But clicking on page 2, and having the slow load feature set; both gave the same result, no fallback image.

After I stepped away from it; the ‘light-bulb’ went on.
We already figured ajax was being used, and more then likely as such probably just loading in the data again. After looking at the data-attributes generated and realizing that

Because AJAX is already used in WordPress’ back end, it has been basically implemented for you.

I just needed to FIND where Jupiter was calling wp_ajax() on post loops.
ended up finding /framework/helpers/load-more.php

After some variable dumping and console.log push(s) I found the problem.

The templates I had been editing and making changes to; were not the templates that were being called. Each time a new page was selected; a new wp_query was called, accounting for existing data-attributes (to skip those posts).
Then the themes ‘shortcode’ mk_blog is called with some global attributes and some of the existing attributes; but not all. The shortcode was calling the default loop style, not the one I had created.

So I just had to redeclare the $atts['style'] to my new style.
Because here is the shortcode/view call: mk_get_shortcode_view($atts['shortcode_name'], 'loop-styles/' . $atts['style'], true, $atts);

I concur, as far as the plugin goes, the problem is resolved.

Concerning Jupiter:
data-page-attribute[#] is main container;
the pagination using onClicks to alter the page-attribute; and yes I agree must be pulling the specific posts from database again; because your plugin adds the fallback image to first page; I click page 2; posts appear but no fallback image; I click page 1, and even though they had fallback images they no longer do. Suggestion what you are saying, page is not re-loaded, just new data via Ajax.

I’ll most likely hard cord something into the templates now; but I was trying to save time : P lol.

I’m playing around with the templates right now to achieve the fallback image in a another manner – similar to my portrait vs landscape issue with it.

If I have more time at a later date; I will attempt/play around with what you are talking about as well; maybe save someone else time at some point. But for now, I must trudge on to other tasks as well.

Thank you for your time and effort

• This reply was modified 7 years, 8 months ago by goodyis. Reason: marked as resolved

I tried on a development site – same plugins and articles – to use a free theme Twenty Seventeen; and your plugin does seems to work as expected; all posts missing a featured image get the fallback image.

Any ideas on how to call your plugin from the theme upon pagination; because something is occurring with the Jupiter theme that is not calling your plugin when a new page from the posts are listed.

Or maybe what hook are using to call your ‘actions’ so maybe I could move to one my theme hooks?

It may very well be an issue with the theme; I’m leaning towards that, but wanted to know if you had run into this before. I will be testing a free theme on a stage environment. If I could get an email from you, I would send you a link of the live site.

1 -> the fallback feature image isn’t getting applied to all posts; unless I set the page/template/settings to display all posts. Meaning:
Lets say I’ve got 30 articles for example. The wp-settings are to only show ten at a time; thus causing pagination. The fallback feature image gets applied to page one. The fallback featured image does not get applied to pages 2 or 3; regardless of pagination ‘style.’

2 -> The theme is not on the free theme repository.
It can be found: https://themeforest.net/item/jupiter-multipurpose-responsive-theme/5177775
An example of the ‘default’ loop for it is here: https://demos.artbees.net/jupiter5/blog/blog-modern-full-width/
I will be testing theme twenty seventeen on a stage environment soon and will post results here.
If I get your email – I will give you a link to the live site

3 -> I’ve customized the blog loop templates to read-in the images size; then calculate if the image is landscape vs portrait view; and then alter the output accordingly. The template files for the ‘archive/category’ pages use the templates; and so does any call to a blog loop. Its working as expected.

Also your plugin is working as I would have expected, with the exception that any paginated pages/post loops to get the ‘fix’

It has been two weeks guys; script is still hanging.

I did yesterday at 2:25PM with the subject “In regards to post-8836592”

I Just added two more screenshots; because it shows 1.5hrs load time for one resource and 2 hr for another.

They still didn’t load they just cancelled themselves.

I’d rather not post them on here.
Could I get an email address to email them to you?