Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter tfooq

    (@tfooq)

    The Block Visibility plugin did exactly what I needed (and then some). Thank you!

    Thread Starter tfooq

    (@tfooq)

    Yeah, I removed it because it wasn’t working. I can’t do this right now, but I’ll try that plugin later and reply here with the results. Thanks.

    Thread Starter tfooq

    (@tfooq)

    Thanks. I look forward to a good stock block display control scheme since I’m pretty much fully committed now to TT3. In the meantime, I’ll check out that plugin. Thank you for that.

    I did try changing it to max-width, but then it also hid the search in the navigation overlay. So that code is not actually differentiating between the body content and overlay menu content I think. I want to hide the search block in the navigation menu on screens wider than 782px (the point my sidebar moves below the posts), but I still need the search block to appear in my sidebar above 782px. The search block just does not work well in the navigation on desktop (it’s very buggy, which is a whole other topic). This is always where I get lost working with CSS. I’m a writer primarily who dabbles in web design just enough to get my site working. I’ll try the plugin you suggested when I get a chance. Thanks for your help.

    Thread Starter tfooq

    (@tfooq)

    Thanks! This is almost there, but it also hides the search bar for the desktop view. I am very novice at CSS, so I appreciate the help. I am OK with the search bar disappearing from the “side” bar on mobile if it appears in the navigation instead, but I definitely need it to appear on desktop.

    As a side note, I really wish TT3 and/or the Gutenberg site editor attached an option to every block allowing users to set visibility based on screen width. This is functionality I keep wishing I had over and over again. I’m sure I can bang my head against the wall trying to figure out the CSS to make it happen, but that doesn’t seem to be in the spirit of the block theme editor.

    Thread Starter tfooq

    (@tfooq)

    I did try adding the comments block, but that just added the whole comment thread to the home page, which was not what I wanted.

    However, I figured out the issue. The post-comments-count block, which is part of TT3 by default, is not in the WordPress core. You need to install the Gutenberg plugin for it to work. This was very confusing and was not noted anywhere that was obvious to me.

    Thread Starter tfooq

    (@tfooq)

    One simple example is Theme My Login. They have a login/logout widget that not only displays the login/logout link but also includes the text “Welcome, [user] | Logout” for users who are logged in. Clicking your user name takes you to their themed profile editing page. It’s a nice feature. I contacted them about this, and they told me widgets still work as legacy widgets. I replied that this isn’t true with block themes that only use the site editor like TT3, so hopefully they look into it.

    Another one is, unfortunately, an abandoned plugin. I know I need to replace it with one that is still maintained, but it’s my events calendar and will require a lot of work to transition. It has a widget for showing the next handful of events on the sidebar, and the only hack I have been able to get working causes a bug the breaks a different calendar feature. I’d love to have a temporary bridge until I have the time to take on the calendar transition project. I assume there will be a lot of potential TT3 (and block theme) upgraders in a similar situation.

    Perhaps someone else can suggest an easier method, but I typically download my child theme’s files and the latest version of twentyten, then use a version compare program (notepad++ on windows does it well, though there are many others) to see what has changed and add the updated code to my child theme files while leaving my personal changes intact. It’s a bit tedious, but I don’t know of another way to update everything except what I purposefully changed.

    For those who found this thread first, I resolved this issue by updating to the latest version of twentyten. Here’s that thread: https://www.ads-software.com/support/topic/comments-not-displaying-after-update-to-5-5-2/#post-13258915

    Aha! Updating to twentyten v3.1 did fix my issue. I’m sorry I doubted the team.

    I am also having this issue. Comments display and function perfectly on mobile (using wptouch) but not on desktop using the twentyten theme. Site: https://www.seattlebikeblog.com/ I am too amateur to know how to even know where to begin to fix this. I’m using a child theme based on twentyten v 2.9. I am going to start the work of updating my theme to 3.1 (most recent) and will report back. But I’m not hopeful since my version isn’t that old…

    I’m having the same issue. Tapping date on mobile (iPhone, at least) does nothing. The other fields work, but date is kind of important.

    EDIT: Here’s my calendar (problem is mobile only, desktop works): https://www.seattlebikeblog.com/calendar/

    It may be a conflict with WPTouch, since it works (but is not very mobile-friendly) if I toggle to the desktop version.

    I’m very disappointed in the Frontend Submissions plugin. How can there not be a mobile-friendly mode yet? It’s almost 2017! If there were an option to have it display as a plain form instead of a pop-up, that would probably fix it. But I can’t figure out how to make this happen. Does anyone know a solution?

    • This reply was modified 7 years, 11 months ago by tfooq.
Viewing 11 replies - 1 through 11 (of 11 total)