Forum Replies Created
-
AuthorReplies
-
September 21, 2015 at 5:21 am in reply to: How to use WordPress oEmbed to embed video in Layout Builder #23245
bartwindrum
ParticipantThank you! Putting the urls on their own lines (where they evidently were before) worked. Maybe editing the page somehow mucked w/it’s content, eliminating the breaks…
I added the 2 snipped lines just now anyway. All four vids still now appear and play. Thx again.
September 20, 2015 at 1:12 am in reply to: How to use WordPress oEmbed to embed video in Layout Builder #23234bartwindrum
ParticipantDuh! (sorry ’bout that!) http://axiomaction.com/speaking/
There should be 4 on this page.bartwindrum
ParticipantWell I solved it. Paypal button code when inserted adds several blank lines above and below the the buttons and below the code in text view, resulting in layouts that are needlessly long due to all this extra blank vertical space. Trying to tighten it up by removing those spaces somehow, for some reason beyond me, mucks with the code resulting in all this aberrant behavior. Guess I have to live with the funky layout.
bartwindrum
Participantbtw I tested a little more broadly by making a new blog entry. That *does* appear on my wife’s computer, hence my suspicion that something about my panel construction is causing this very strange anomaly…
January 17, 2015 at 6:33 am in reply to: Layout Builder 2.0, separated elements from Edit Page, template sync #20144bartwindrum
ParticipantJason, in the new environment under WP 4.0x, the page content takes noticeably longer to load — and a very long time to load when that content is tabbed. Do you know if this is due to WP, Builder v2, or some interaction between both?
btw, I can edit page content just fine and my pages are linked to templates.
December 5, 2014 at 2:55 am in reply to: Layout Builder 2.0, separated elements from Edit Page, template sync #19525bartwindrum
ParticipantAha, I get it. More flexibility. 🙂
September 25, 2014 at 11:33 pm in reply to: Paypal button with dropdown menu choices results in Paypal Error #18778bartwindrum
ParticipantThe menu’d button is highly erratic; works in some page layouts and not others. Big drag to deal with. For anyone reading this with interest, here’s my solution:
1. make separate button for each webinar event, including a bundle option
2. make a panel and center the content within it
3. use dashed divider between each event
4. format sensibly and tighten spacing btwn description and following button in the WP UI *visual* view (where you can strip an extra space that doesn’t appear in text view).This scheme is the only way for a) reliable button performance in the Paypal cart, and it also makes for a very clean/clear display on mobile devices esp phones. Using a panel gives me the option of stacking panels in sequence should I offer more than one webinar series with concurrent signups.
September 24, 2014 at 11:17 pm in reply to: Paypal button with dropdown menu choices results in Paypal Error #18769bartwindrum
ParticipantOK, the other site wouldn’t summon the cart; I don’t know/recall enough about paypal config to untangle that. However:
Using paypal’s default labeling on a new menu’d button *did* work. As did editing the menu item names down from something like “Webinar 1, Obstacles 1—3 …” to something simpler just worked — in a blank test page. The label section of the code is now:
Select Your Webinars
Webinar 1 $35.00 USD
Webinar 2 $35.00 USD
Webinar 3 $35.00 USD
All 3 Webinars $99.00 USDOK; I just put the simplified button in the tab and *it worked*. Apparently even though the more punctuated menu labels worked in paypal’s test bed, something about having them inside Akita breaks something. I’ll get around this by listing the details of each session above the buy button.
September 24, 2014 at 10:40 pm in reply to: Paypal button with dropdown menu choices results in Paypal Error #18767bartwindrum
ParticipantNo it doesn’t. I just made a new page using first a default layout then a custom layout and selected one of my builder layouts at random. Pasted only the dropdown 4-item button code in; it failed at the cart in both layouts. Then I added a one-item button below it, in the custom layout. That *did* work. With that product in the cart I tried the dropdown button again, selecting a different item from the menu. As before, it failed at the cart. The cart message always reads:
Error Message
PayPal cannot process this transaction because of a problem with the seller’s website. Please contact the seller directly to resolve this problem.If there’s anything specifically I can ask of paypal that might help shed some light let me know and I’ll call them up.
Meanwhile I have another old site using some other theme. I’ll try dropping the menu’d button in there and see if that works, then report back.
September 22, 2014 at 11:03 pm in reply to: Slider Wishlist: duplicate or image show/hide toggle #18726bartwindrum
ParticipantHah! You may find this amusing; to me the built-in slider is among the easiest of Akita’s things to use. I hope you’re not going to end-of-life the slider plugin! Will the updated Builder recognize sliders made w/the plugin and allow duplicating them?
bartwindrum
ParticipantAh; since I don’t do this sort of site development regularly I forget about sniffing around with diagnostic tools. Argh!
bartwindrum
ParticipantYeah; I discovered that the nesting results in some “extra” raw wrappers that need removing. Not a complaint, but the nested left/right padding begins to make the content layout look weird. Hmm, I recall that we tweaked padding previously—I think, though, in the Child CSS that affects things globally. A solution for my use at the moment would be if I could remove the left/right padding from the columns. Here’s what I mean: without columns, putting content in the toggle results in a column X px wide. Reformatting that space into columns results in a narrower content area because of the padding on either side of the column stack. If I could remove that padding from that object, or page, that’d probably result in a win.
To put this into context, I’m mulling over design issues in terms of user experience—number of clicks and page deliveries. Nesting has the potential to reduce both to one, where I can list multiple events. Columns are required so that the content doesn’t wrap underneath the images representing the programs. That’s the sole reason for them — column 1 holds images, column 2 holds text. I’ve found that columns also help the look of things when displaying on narrow screens.
bartwindrum
ParticipantThanks. I just stumbled across pulling the pipe from the url and it worked. Just wanted reassurance it’d continue working (a silly sounding question to pose, but one never knows…). I’d lose signups only if the url failed to work in the future for some reason. I guess if it works once, it’ll always work.
bartwindrum
ParticipantSorry for the 2nd post but actually I experienced, as I futzed around with things, a mixture of 404 errors and the intended page being displayed but showing tab#1 instead of the intended tab (which is #6)…
September 18, 2014 at 5:27 am in reply to: Interested in Creating What I'll Call a Clickable Floating Overlay #18666bartwindrum
ParticipantJohnmos, thank you. I was beginning to mull over widgets before realizing that my site’s homepage is configured for no sidebar. Hah! Thus Layered Pop-up seems interesting. Huge overkill for my design needs — either headline, subhead, and button, or display a graphic and assign a url to it. But obviously a well supported and Envato-trustworthy option.
-
AuthorReplies