Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Just coming here to let you know that this is the exact question I was looking an answer for.

    So let us consider here. Maybe together we can find the best possible answer:

    WP TT5: default theme, more open, more inclusive. Will have features that WP officially supports, if nothing else but to showcase them.

    OllieWP (the free version): great design out of the box. Will always want you to upgrade to the pro version, which is yearly license based. OK but not for me.

    I personally am very much tilted towards the default theme, given I want to make my own patterns and blocks and template parts. I dont know if YOU want to do that? I know that I’d have to make changes to OllieWP as well. So as long as I am making changes, might as well go with the default theme and continue my learning journey that way. And have more stability that way.

    You mentioned 10 yr plan. That alone means default is the option. WPOllie, though will probably be around 10 yrs from now as well, is dependent on like a couple of guys at best. It is a commercial venture and profitability can make them take a (valid) decision of closing it down etc. So there’s that.

    Thank you Mike. But I installed a child theme on a stand alone, it was OK. I installed the same on a multisite (with the twnetysixteen theme there as well of course), it gave me the integration notification.

    I double checked on the stand alone site (latest WP version, WooCommerce, 2016 theme, mychild theme)… it was working fine.

    But on the multisite, it was giving the integration notification. I had to declare support in the functions.php for the notification to go away. I still think there is something wrong with the display over at the multisite.

    What gives? Any difference?

    Isn’t twentysixteen compatible with woocommerce right out of the gate? Or do we have to declare support for woocommerce?

    OK so this is pathetic.
    The .htaccess file (that I was editing on notepad.exe on win 8) had formatting!!!!!!!!!

    The moment those formatting marks were removed, all is working well! Alhumdulillah!!

    Thank you 1a and ipstenu for the help…

    P.S. I was not able to see those formatting marks, only the support crew at Hostgator saw it and removed it. If notepad doesn’t catch them, what other free, simple text editor can one use!?

    That’s… weird. You didn’t have an old, lingering version of Multisite on the server, did you?

    Now I didn’t say that. :/

    I really don’t remember since when I have WP on the said domain (i.e. the designby.momekh.com domain). I have been upgrading of course, but the multisite was only after I had 4.0, so fairly recent.

    Right now, the problem is simple in its severity: The moment I have ANY .htaccess file, a 500 internal server error on all sites (on the main designby.momekh.com and all subsites — I have only three now, all for testing purposes).

    I can access the htaccess via Network Setup. I have tried that. And pretty much all variations I can find. But like I said, any form of .htaccess and I get a 500 internal serve error.

    There is a certain @ipstenu (Mika Epstein) that I see on all matters of multisite issues… a person like that can help perhaps?

    I am stuck pretty bad here.

    Hmmm…

    I have wordpress installed on a subdomain. Just for that, do I need more instructions in the .htaccess?

    After I’ve installed WordPress on the subdomain (which is http://designby.momekh.com)… I installed a multisite so I can have http://designby.momekh.com/site1 etc. I have only added .htaccess for this scenario. Are you saying that I need to update .htaccess to reflect the original subdomain installation of WP itself?

    Am I even making sense here? :/

    Go to your Network Admin area.
    What you’re looking for is in

    Settings > Network Setup.

    cheers!

    OK, as I was typing this I was trying this out.

    This problem only happens when I was using a previously uploaded gallery. No images were found to be attached.

    I added a new post (post-format: gallery) and added a few pictures in it, the above code now prints the post parent!

    Now I wonder if this problem is bigger than it looks: what if someone installs my theme, and already has gallery-format posts? Will this code not work for them? Hmmm… Maybe WP somewhere “Builds” this, and one can do a “refresh” of all gallery items and post->parent vars?

    Akkkhh! :/

    I am developing a theme. post_parent is reverting pack to the attachment itself. I am using twentyfourteen’s function here:

    <p class="small byline">
      Parent Post (for this attachment):
      <span class="parent-post-link">
       <a href="<?php echo get_permalink( $post->post_parent ); ?>" rel="gallery">
    	<?php echo get_the_title( $post->post_parent ); ?>
       </a>
      </span>
    </p>

    I am using add_theme_support( 'post-thumbnails' ); as well.

    Any ideas? :/

    OK, so the thing just started working again. On its own.

    This is not the first time technology ghosts have wrecked and then saved the day. :/

    Alhumdulillah

    Thank you so much for the help again!

    Makes sense. I have a caching plugin.

    Also, I have a SQL file backup (via a backup plugin).

    Here’s what I’m thinking of doing:

    • Hit up Hostgator, and see if they can fix this?
    • If that fails, I can log in via PHPMyAdmin and try to do something with the sql backup that I have

    Frankly, I don’t know what kind of data the .sql file will have. Will it have images as well!? It’s a image-heavy site. Hmmm…

    Thanks again. 🙂

    There is one thing though:

    The site has an online ordering form. The whole thing is working!!

    IF the DB is gone, then how come the front-end is working??

    The only problem is while accessing wp-admin
    Maybe there is hope? Any more clues?

    Hills it is then. :/

    Thanks @catacaustic… I was fearing that was the only way out of this.

    Prodos, thanks for that. Although I haven’t checked if those were the changes made on my side.

    But on the whole, what are we saying here? That Akismet’s Readme file _was_ written for 4.0, and then later was updated to read the correct WP version?

    And that readme file changed in WordFence repo,and because of that change, a warning was issued?

    I shudder to think that akismet automagically changed the readme file on my installation and then wordfence caught that?

    Thanks y’all for the comments so far.

Viewing 15 replies - 1 through 15 (of 25 total)