Ximbalo
Forum Replies Created
-
Forum: Plugins
In reply to: [The Events Calendar] Adding a Featured Image to Events PageBrian,
OK — Got it — I’ll take a closer look at the Themer’s Guide and thank you for the quick response. It certainly does seem like it will be best for me to create a new custom template that does include a full-width image at the top of the page.
But, for the long-run — please do consider trying to update your plugin to make it possible for someone to create a standard page in WordPress, and drop your Events Calendar content into that page… rather than forcing every client to essentially re-theme your plugin to “fit and work” w/in their already working layouts, and themed pages.
Thank You,
XIMBALO
Forum: Plugins
In reply to: [Media Library Folders] Cannot Remove Old FolderEmail on it’s way — thank you.
Forum: Plugins
In reply to: [Media Library Folders] Cannot Remove Old FolderAlan — certainly, and I DO appreciate your taking a look at it.
But unclear on how to send a private response here…?Forum: Plugins
In reply to: [WP Donate] Donor List Not PopulatingOne more issue to resolve is that of customizing the SUCCESS/ERROR response area. Even on success you are forcing the content there to be returned like this:
<td style="color:red;" colspan="4"> -- Success Message Here -- </td>
But RED text is so commonly used to indicate an error and so I suggest to you that this should NOT be hard-coded this way.
SO if you were instead of that, do the following:
<td class="response" colspan="4"> -- Message Here -- </td>
You would make it much easier for us to use normal CSS to customize the output. Instead I had to add this to my CSS:
#donate_form tr:first-child td { padding: 10px; font-size: 18px; color: #face38 !important; background-color: #292929; }
Which is not only quite awkward, but also makes the assumption that your plugin for all future revisions will ALWAYS use the very 1st row of your form structure table, and I have to use the !important indicator to override your hard-code styling.
A more standard way to style this would be to use a CSS class that identifies the container being used for status responses…
Thank You,
Thank You for that. Doing so now.
I am having the same problem trying to use your plugin, and FYI — I really think you should look a little more deeply into this, b/c when I try to Google this message, you can quickly see how many other ( hundreds ) of sites are showing the error:
https://www.google.com/search?q=+Invalid+argument+supplied+for+foreach%28%29+plugins%2Fwordpress-simple-paypal-shopping-cart%2Fwp_shopping_cart.php+on+line+80I’m bummed b/c yours looks clearly like the best solution for my current requirements… but I can’t use it until you fix this — so I’ll have to go and try/test all the other lesser-looking plugins for now. Please let me know if or when a solution is in place — so I can switch back to using your plugins instead.
Thanks,
XIMBALO
Forum: Themes and Templates
In reply to: [Ryu] Fixed Menu BarKathryn,
Hi — Thanks for the reply — and yes that is what I meant.
To a partial degree, you can see the update that I have already applied to toward this end here: https://ice-catcher.com/I agree with your suggestion — I just wanted to check if you already had any pre-existing solutions for this idea.
Thanks.
Forum: Plugins
In reply to: [AI Responsive Gallery Album] AI Stylsheet Changing my Theme Styles Site-widePost Note: I think that perhaps you had these styles for a “Demo Page” and they might have accidentally gotten included in your actual plugin release stylesheet as well, perhaps? B/C I can’t imagine that you would intentionally add global scope body, a, *, and box-model style changes in your plugin, right?
Forum: Plugins
In reply to: [AI Responsive Gallery Album] AI Stylsheet Changing my Theme Styles Site-wideYes, no problem — however it is very easy to isolate where in your plugin’s stylesheet the problem occurs. You have added to your stylesheet styles that effectively override, modify or completely change the way an entire WordPress site will appear, including the following lines ( in your ai-responsive-gallery.css file )
1. Asterisk Based Global Styles:
*, *:after, *:before { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; padding: 0; margin: 0; }
The above lines effectively change the box-model rending of every element throughout the website. If a website has been styled based on standard box-model assumptions of Width + Padding + Margin + Border — then the lines above will re-factor everything everywhere to NOT use the standard cumulative box-model mathematics.
2. Body Tag Style:
Your inclusion of a body-tag style in your CSS overrides the default styling of the entire website — again everything changes site-wide.3. Global Scope a { … } and .container { … } classes:
Your inclusion of global scope a { } style means that every link everywhere on the website will now inherit your base a-tag style. Your inclusion of the .container {} styles means that if a a website already has a .container class ( one of the most used content area wrapper classes in the world ) — yours will likely override it even to the point of making every page on the website completely fall apart.SO — there you are.
Unfortunately — I cannot include a link for you to see the site where we tried to use it — as we had to finish the site and make it ready for delivery to the client. There was absolutely no way to do this with your stylesheet overriding our styles globally everywhere.However, in order to see which styles I am referring to that your plugin brings to bear upon a site, please just look at this file that i have saved here for the purposes of this message:
https://thecloudpool.net/Assets/ai-responsive-gallery-album/css/As soon as your ai-responsive-gallery.css file is included it overrides the most fundamental, global CSS styles used by a website. Please, consider removing the a, body, .container, and ESPECIALLY the global asterisk-based styles from your stylesheet.
Otherwise your styles are the equivalent to “a website style takeover”.
Thank you and best regards…
XIMBALO
Thanks for the update. I think that, ideally, it would be good to add a way to track what page(s) your plugin shortcode gets added to. Then, for those pages, load your styles into the header, and your scripts into the footer. I will have to do some reading and testing on a demo plugin to see if I can achieve this kind of conditional output.
Thanks for the response!
Regards,
XIMBALO
Forum: Plugins
In reply to: [Maps Widget for Google Maps] Two Pins appear in Thumbnail MapYes, clearly the PIPE was the issue.
Thank You
Forum: Plugins
In reply to: [Simple Staff List] Show individual member of staff from list by idI have a site I am building a for a teen girl’s softball team, here:
https://socalknuckleup.com/You can see on the home page that we’re trying to add a list of team management members, as clickable links to each person’s personal profile. In order to create this kind of list I had to alter the list template as follows:
[staff_loop] <a href="https://socalknuckleup.com/staff-members/[staff-name]" title="[staff-name] : [staff-position]"> <img class="staff-member-photo" src="[staff-photo-url]" alt="[staff-name] : [staff-position]"> [staff-position] : <b>[staff-name]</b> </a> [/staff_loop]
… then add jQuery to replace any blanks in the [staff-name] part of the link URL with dashes, thereby achieving a list of proper post-name clickable links to each staff member profile.
I could not see an easier way to do this. SO…
Q.1 — is there an easier way to do this?
Q.2 — how can I modify the individual staff member post type output to show all their profile information?In other words I simply want to achieve a clickable list of staff members, each item of which goes to a proper staff-member full profile, contact info & bio page.
Thank you,
XIMBALO
Forum: Plugins
In reply to: [WP Publication Archive] Publication List in Admin Panel only shows latest 5No answer to this issue yet? Can I hope for a response?
Yes, I have moved my posts to the Pro Support page, thank you.
For me, yes… I was able to format the sidebar entries ( for existing “demo” events ).