Forum Replies Created

Viewing 15 replies - 16 through 30 (of 339 total)
  • WordPress permalinks will take care of things by itself, and slugs arent exactly stored in your database, so i guess its ok functionally.
    Do remember that every post and page published has few fields like ‘ID’, ‘post_name’ and ‘guid’ which are unique to themselves.
    also posts popup in your feeds (also where guid field plays a role), whereas pages dont.
    and if you have a sitemap thats autogenerated then new entry gets added and might result in duplicate entries for same slug – bots crawling, reporting – bad SEO?!

    alternatively, for enabling comments in pages, why not edit your theme files (most probably page.php) and insert the comments code/template?

    You will have to make changes to your code files. I dont think a plugin will help and is needed anyways.

    But am unclear as to what your permalinks are like;
    and what is say for example this – https://www.kieshetsnel.nl/selena-gomez-taylor-swift/.
    Basically, is it a post or a page?

    I assume you are using Sydney theme?

    So, if its a post, you will need to edit content-single.php:

    <div class="entry-content">
    <?php the_content(); ?>
    <?php wp_link_pages( array('before' => '<div class="page-links">' . __('Pages:', 'sydney'),	'after'  => '</div>', ) ); ?>
    </div><!-- .entry-content -->

    insert a <a href="https://www.kieshtsnel.nl/random">Next &rsaquo;&rsaquo;</a> before <?php the_content(); ?> and check.

    and if its a page, edit content-page.php, where you will find the same code snippet, and you need to make similar changes.

    if its a custom posttype then we will have to look at it likewise.

    Pls edit with care, possibly on child theme and take backups.

    Am curious to know how you got the redirects done from https://www.kieshtsnel.nl/random to a random post. whats the htaccess hack? would be glad to know the code. ??

    Cheers…

    Looks like you got a paid theme – https://getnoticedtheme.com/#pricing

    So better ask them directly for support here – https://members.getnoticedtheme.com/wp-login.php

    All your thumbnails on homepage are of 150x100px resolution.
    So i guess your homepage is taking the default value of thumbnails for images and displaying.

    Check for the following in your functions.php file in your theme folder:

    add_theme_support( 'post-thumbnails' );
    add_image_size( 'thumbnail', 150, 100, true );

    ^ this checks if your theme supports thumbnails. And the second line specifys the image dimensions of thumbnail.
    If these exists, they will override WordPress default settings!

    Since you checked with multiple themes, i guess we will look into WP settings next:-
    Go to your Dashboard -> Settings -> Media.. Change the thumbnail size to a higher resolution, say 450×300.
    Save Settings and check with next post.

    Note: These settings will be applicable to all new posts which you further publish, old posts WILL NOT get effected!
    I guess there are some plugins which may help you with regenerating thumbnails with new dimensions for old posts. Am unsure. Check.

    PHP has an upload filesize limit and memory limit.
    so if you have access to root on your server, then try editing php.ini and change variables memory_limit, upload_max_filesize, post_max_size.
    also there is a PHP memory allocation variable for WordPress exclusive. for that, use define( 'WP_MEMORY_LIMIT', 'xxM' ); define( 'WP_MAX_MEMORY_LIMIT', 'xxM' ); in wp-config.php file.
    you can readup on them before editing. edit with care!
    also remember to restart php services (and maybe apache) for it to work.

    PS: your images are horribly heavy! i checked https://sofia.com.sg/flaxseeds/. the first image is 6000x4000px and has a freaking 8.4MB filesize! this will increase page loadtime, hit SEO, etc. when we code, except for very few images which are graphic heavy, we keep all images in 100-700kb range (in bout 3-4000×1-200px range). food for thought.
    how to: try photoshop. open your image and go for ‘save for web’ in file menu. try saving with jpg->high parameters and with bout 1920×1200 or 1800×1200 or so image res. you should end up with a sub <500kb file with no clarity loss.
    and then you can change jpg quality to 100% in WP so WP doesnt crunch it. that would be by adding filters in functions.php

    Thread Starter shadez

    (@shadez)

    sorry could check back on this thread only now. Looks like you got it solved. So will leave it at that for now. ??

    Thread Starter shadez

    (@shadez)

    aah.. my understanding was wrong. i thought post-formats are other post types – ie different from single/standard post format.
    so i guess we can use conditional checks over get_post_format and has_post_format and fetch partials. thanks for the code.
    and thanks again Alchymyth for replying. ??

    your theme is: https://themes.themeprovince.com/cluster/

    So check with your theme devs at ‘Theme Province’ for support, esp since yours is a paid theme.

    i guess this is support guide: https://help.market.envato.com/hc/en-us/articles/202500424-How-Do-I-Get-Support-For-An-Item-I-ve-Purchased-

    not at all.. i guess my answers to your questions and suggestions got mixed up. lemme try clearing things up with more like a good coder perspective of things..

    primarily, you are using the opensource and self-managed WP, so it goes a great deal in understanding wordpress file structure and basic working.
    so i will assume for now that you know that ‘wp-content’ folder is kinda like ‘your area’ – holds your themes, plugins and media contents; and everything else is part of core, except wp-config.php and htaccess files at root.
    the above is ofcourse for front-end code, there is also the DB which is totally you.

    now going back to development,
    Theme –
    1. use relative URLs in code – php/css/js,etc.
    2. try to contain all code implementation within your theme folder and avoid external calls to other files placed randomly on server.
    3. goes without saying, good coding standards and understanding WP APIs matter.
    4. have a good understanding of wp-config.php settings (siteurl, homeurl and such) and keep an eye on functions.php for any code that might mess up things. esp if suing 3rd party themes.
    5. use good editor and utf-8 encoding.
    Plugins –
    1. use only the most necessary ones for development purpose. you can install others (like SEO) later after going live. the beating a fresh site takes on SEO front after going live is bare minimal so you neednt worry.
    2. preferably use trusted/common plugins. some of them create a nightmare while porting or in future while upgrading etc.
    Contents –
    1. images and other media files uploaded to your local server would go into the database as absolute URLs through post data. this is the reason why you need to run sql queries later on after porting.
    2. so depending on the type of site you are developing (like static, corporate or a proper CMS blog), streamline your work and check how much of content filling should be done locally and how much on live server. also remember that there are plugins which help in showing a ‘coming soon’ or ‘under maintainance’ frontpage while you get to work on the files in background on live server. so this i recommend based on personal experience – if you happen to use html/php code within the post content, DB export/import might trouble you later.
    other –
    1. its always good to have a staging server with similar mapped platform as your live server. also code version control.
    2. too many changes to settings, permalinks, etc on wp-admin dashboard can confuse you after migrating. so try keeping that too to minimal and noted down for later.
    3. permalinks – understand them, disable/enable while migrating.

    your server – go for a good host and a hosting plan, good config, have the DNS mapped and all.

    so basically, a good understanding of WP, good coding practice, and good server will ease things up which migrating.

    for migrating WP:
    heres the codex – https://codex.www.ads-software.com/Moving_WordPress
    and heres a good tutorial – https://www.smashingmagazine.com/2013/04/08/moving-wordpress-website/
    the codex will give you some healthy pointers and reminders, and the smashingmag tutorial i found more relevant and professional than the other link you shared. no offense to wpbegginer, it was my favorite during my initial days.

    clear?

    Read this: https://codex.www.ads-software.com/Installing_Multiple_Blogs

    subdomain multisite install is definitely “easier” to install and manage and is commonly used method, though i cannot judge the better of em.

    the answer is quite broad here but answering specific to your questions:
    > slow and page not opening – type of hosting and which host matters. also DNS propagation takes time, and same goes for permalinks. calculate like a day or even 2 for the URLs to set in properly.
    > assets?
    > code – impossible if you havent hacked the core. but core files WILL change (during upgrade, etc) – hence, never hack the core. themes and plugins are the only external code which comes new into WP installation 99.99% of the time. or wp-content folder to say as a whole including media data. and if you dont see them, re-FTP them in.

    apart from these, working on a staging server, using relative URLs, version control etc are methods i would recommend for you now..
    migrating themes and plugin (esp ones with lot of settings) is a pain and needs manual re-checks.
    also, unless yours is a full-fledged CMS site, for static or smaller content sites, create pages and posts post installation on server. easier and less sql hassle (esp if you got html code within) this way..

    you will need FTP access to your webserver to access the folder.
    wp-content is one of the 3 folders under wordpress root folder.
    heres an image of folders: https://www.wpexplorer.com/wp-content/uploads/WordPress-Root-Directory.png

    Forum: Hacks
    In reply to: Coding help

    server errors could be htaccess issue etc. for workaround, try creating a page template in your current theme directory say anything.php with content:

    <?php
    /** Template Name: Check cURL
    **/
    phpinfo(); ?>

    .
    create new page and choose this template from right side and then publish/preview and check. ofcourse delete it later.

    PS:
    checked with WP all imports support team for any help?
    any relevance here? – https://xml-import.eu/datafeed-synchronization-module/

    Forum: Hacks
    In reply to: Coding help

    Woocommerce right? Woocommerce is csv friendly so maybe convert it?
    > https://www.luxonsoftware.com/Converter/XmlToCsv

    And/or use some plugin to import:
    > https://www.ads-software.com/plugins/woocommerce-csvimport/
    > https://www.ads-software.com/plugins/woocommerce-xml-csv-product-import/
    > this looks like paid but good: https://www.wpallimport.com/

    I havent tried any of these plugins myself. just giving ideas. Hope this helps.

    What you are looking for isnt exactly wordpress stuff.
    You will need to edit your header.php file and add custom code to it for this to work.
    The link ‘Kids toy theme’ you have provided doesnt work for me. Provide link to your actual website so maybe i can look into it.

Viewing 15 replies - 16 through 30 (of 339 total)