zinnmark

Yes, still having the issue and new problems showing up with version 1.1.3 including test donations not showing up in the table and PayPal gateway not showing up either. I’ll be sending you those login details shortly.

Thanks,

Mark

Thanks for getting back to me. Yes, I’m still having the issue using latest update version 1.1.3. Also, test donations are no longer showing the table like it used to. I reverted back to version 1.1.2 due to a separate problem where submitting a donation resulted in skipping the PayPal gateway altogether and going straight to the receipt page. I’ll send you login details shortly.

Mark

For example, here is code I’m seeing in Firefox for inspecting an input box element:

.charitable-form-field input, .charitable-form-field select, .charitable-form-field textarea {
    width: 50%;
}

This code is in line 78 of charitable.css but for some odd reason the browser shows it as _forms.scss:9 so it is difficult to tell where the declaration is. The same thing happens in Chrome.

Likewise, for the donate button, I see the following:

.donate-button {
    padding: 6px 24px;
    border: medium none;
    background-color: #F89D35;
    color: #fff;
}

The code starts in line 63 of charitable.css, but Mozilla shows it as _campaign.scss:84. However, the change will take effect if I edit charitable.css line 67 and set the color value to black (#000).

I’m have trouble editing the CSS as well and I wonder if my problem is similar to yours. Just today, I was able to make a number of style changes to charitable.css, but for reason that file suddenly quit displaying in my browser (no longer visible on element inspection). In Chrome and Firefox, I noticed the CSS declarations were present but the stylesheet changed to _campaigns-grid.scss and _forms.scss depending on the element. The appearance looks the same, but I could not figure out a way to change it. I tried reinstalling the plugin but that didn’t fix the problem. I need to make one change in particular to the donation button because the word “Donate” matches the background color, making the text invisible. I’m stumped on this and I’m hoping someone can point me in the right direction.

That’s too bad. I can see this plugin isn’t going to work for me any longer.

So, the stylesheet for your plugin, unlike most other plugins, does not have any selectors to modify formatting for the field alignments. Correct?

Mark

FYI, testing this plugin further on a clean installation of WordPress, I found out that formatting problem still exists using the WordPress Twenty Fourteen theme. However, when using the Twenty Fifteen theme, the formatting looks fine in part because the field labels are above the input boxes. However, it is still not clear to me what CSS code is making a difference. Please advise.

Mark

Currently, I don’t see a way to fix this using my theme’s own CSS. I looked over the code for 4.0+ styles in styles.css in /plugins/seamless-donations/css folder but could not find any lines of code to tweak. Using Chrome to inspect the element for the “first name” field, for example, reveals the the following:

<div id="_dgx_donate_donor_first_name"><div id="_dgx_donate_donor_first_name-error-message" style="display:none" class="seamless-donations-error-message-field"></div>First Name:<input type="text" name="_dgx_donate_donor_first_name" value="" size="20" data-validate="required"></div>

Mark

I posted wrong link by mistake–here is the correct link:
https://www.thencri.org/donate-now/

I just checked this forum and found out you were trying to help me despite my lack of response. So I really appreciate that. I was trying to use the “Get pre-filled URL” function that allows you to insert a value into a field on the Google Form. The 1729249446 number is the assigned value of the specific field that I need to insert a value into. The value is a unique ID number that comes from a URL parameter on my site. If I type a value into the string manually, that number gets entered into the form without any problem. So, it appears the link your sent me is something that may work, using a PHP hack with .$_GET[”]. I would need to adapt it a bit to fetch my URL parameter. I understand the gform code was deprecated, but it seems to offer the functionality I’m looking for.

I’ve tried other video plugins and this is the best and most intuitive plugin available that I know of. Hopefully further updates will be forthcoming, but I agree, a response from the author is needed to clarify the development status of this outdated plugin.

Ken,

Removing those quotes worked for me as well. Thanks so much for posting this workaround!

Mark

Hi Tom,

I see now, thanks for the clarification. I had missed the trailing semi-colon. Unfortunately, including it still did not solve the problem for me (I tried ‘& # 8217;’ with spaces and ‘ᰱ’ without spaces).

Currently, my lines are as follows:

‘
$numb = $arguments[‘videoId’] ;
$numb = str_replace(‘& # 8217 ;’, ”, $numb);
$numb = str_replace(‘& # 8242 ;’, ”, $numb);
$video_details = videoDB::find_video( $numb );
‘

Hi Tom,

Thanks for posting your solution, but it didn’t work for me either. Entering numbers returned the same result: [Gallery not found]. I’m curious as to why you substituted xxx, yyyy instead of simply typing in the &#8217 and &#8242 into the code itself. Are there other possibilities for substitution that might fix this problem?

Mark

I’m having the exact same issue with TML version 6.2.2. Clicking on register link or lost password link directs back to my blog post. I rolled it back to version 6.1.4 and the problem went away. I have not experienced any issues with this earlier version, even using the latest WordPress. I assume it is the redirect loop error that others are writing about. It seems to have occurred at some point between these two versions.

I also want to say this is a great plugin, certainly the most comprehensive one I’ve seen for handling all aspects of the user login. All the rest fall way short but this one does it all. It should be integrated into the WordPress package. Keep up the outstanding work!

Best regards,

Mark