Forum Replies Created

Viewing 15 replies - 1 through 15 (of 61 total)
  • Thread Starter johnynla

    (@johnynla)

    For many images storing and then show to website visitors.

    CloudFlare is enough? Or GoogleDrive maybe better? Or AmazonAWS, or GoogleCloudCDN?

    Thread Starter johnynla

    (@johnynla)

    NOT OPTIMIZE, which mean “clean already exist garbage”, but PRE-setup for minimize DB garbage creating!

    • This reply was modified 1 year, 2 months ago by johnynla.
    Thread Starter johnynla

    (@johnynla)

    This plugin is too bulky, I don’t need cache, images optimization, etc.

    Do you know similar simple plugin just with hidden settings?

    Thread Starter johnynla

    (@johnynla)

    By another words it can be named as: “Content Toggle or Accordion Vertical Block with Vertical header”.

    Does anyone know a such Gutenberg block?

    Thread Starter johnynla

    (@johnynla)

    Ouch, open tickets #111… then when this function will be added, at 2055?

    Thread Starter johnynla

    (@johnynla)

    Very simple, just add at side of your “Sticky TOC”:

    1. Bold arrow which will point to the place/paragraph where user stopped reading.
    2. Check marks which will point to the places/paragraphs where user place a bookmarks.

    At the bottom of the TOC add a new button “add bookmark”. (Maybe it must work after cursor placement or text highlighting, or just point to the current (first from top) paragraph.)

    Thread Starter johnynla

    (@johnynla)

    1. Yes, seems it’s a bug/issue.
    2. I’ve already do this, but at the bottom there is a small additional up-extendable unneeded line.
    Thread Starter johnynla

    (@johnynla)

    Seems that you don’t understand nor the question, nor the problem with WP.

    [Firstly] wp_posts and wp_postmeta is the MOST garbage tables which world databases ever have. Especially when you have CPT with 100 CustomFields – if you will store them at wp_postmeta this table will become extra large which slow search etc. Thus it’s better to store CustomFields values not at wp_postmeta trash, but at separate custom table like “wp_Cars”.

    [Secondly] Thus, which column type is better using for they storing? LONGTEXT in terms of professional DB architect it’s completely terrible decision to inflate the DB size when it is not necessary at all, for storing all chosen Terms ID’s of 1 Taxonomy – varchar or tinytext mostly is enough.

    • This reply was modified 2 years, 9 months ago by johnynla.
    Thread Starter johnynla

    (@johnynla)

    Revision for better understanding.

    WordPress with plugin for Custom Fields stored at DB Custom table like Pods/MetaBox/JetEngine/etc.

    Logic:

    1. Custom Post Type (CPT) witch data will be stored at database Custom Table.
    2. Custom Taxonomy with Custom Terms.
    3. Adding to CPT Metabox Custom Fields with possibility to multi-choose of #2.

    Example:

    1. CPT “Cars”.
    2. Custom Taxonomy “Material” with Terms: “Metal, Plastic, Rubber”.
    3. On CPT “Cars” a new post “Audi” creating there are appear a list of Custom Fields, for example field “Material” with values taken from Taxonomy “Material”. User can choose 1 like “Metal” or many Terms at once like “Metal, Rubber” etc.

    Question:
    How is better to store chosen Terms ID’s at Database? But, please, take into account, that this “relationship” type is ONLY 1-side (DON’T need to choose CPT at Taxonomies!). I see next options:

    A) Store at #1 database Custom CPT table at column like “materials_ids” all chosen ID’s as comma separated text. But then is the question – which database column type is better for such purpose (varchar/tinytext/etc)?
    B) Or for such case the better DB design to create a new relationships table? But does it really needs for only 1-side relationship?!

    What pros/cons between A/B methods for DB, WP, data using, searching, etc?

    • This reply was modified 2 years, 9 months ago by johnynla.
    Thread Starter johnynla

    (@johnynla)

    Thanks for the fast answer.

    That’s actually a good question – does the CDN deliver optimized images if they are not uploaded using the media library. I’m not sure, but you can just test it out using something like this:

    https://jetpack.com/blog/why-your-wordpress-website-needs-an-image-cdn/

    But most of WP plugins (as JetPack etc) all the time works as HOOKS TO WP, thus if images was NOT upload via WP Media Library, but upload via ftp/http directly to some folder – suppose not one of the WP plugins will NOT work with them. 🙁

    However, you could just use the CLI like this:

    https://developer.ww.wp.xz.cn/cli/commands/media/import/

    It will make garbage with 10’000 records at wp_posts & wp_postmeta tables. 🙁

    Why use WordPress for this project at all?

    Because I’m a HiTech electronics engineer, but not a web-dev – thus I’m forced to use some kind of web-kits&constructors. 🙁

    Thread Starter johnynla

    (@johnynla)

    There’s no need to speak like that to people @johnynla.

    Say it to your angry brother about his answer:

    Perhaps another software, such as MS Access, MS Power Apps, or FileMaker for Windows would be a better fit for your needs and expectations.

    Truly say – because at 2023 it’s almost useless to have many tables without search – what you didn’t take care of and did not establish a partnership with no one developer of Search & Filtering to add support for Pods CustomTables – it’s again a huge squander of time and possibilities by Pods developers, it’s again your big fault. It must be done at… 2010?

    Thread Starter johnynla

    (@johnynla)

    What you consider a “critical flaw” does not stop many developers from their every day use.

    Answer is simple unfortunately – because they are unprofessional, because most of WP developers self-taught with a lack of knowledge of what is right or what is wrong at DB structure. Very simple, very obvious.

    I’m sorry that we weren’t able to get this sorted for you right now but it’s planned for a future release and could be within 2023 but more likely in 2024.

    It must be when plugin was created – option to store all Custom Pods/Groups/Fields at Pods own custom table(s) – at 2010?

    Thread Starter johnynla

    (@johnynla)

    Sorry for the inconvenience here, Pods might not be the plugin for your specific needs at the moment.

    At …… WP area there is no any alternative. Only JetEngine, but it have another also absolutely critical limits (CPT cant store CustomFields at CustomTables, only at wp_postmeta; ACT can store CustomFields at CustomTables, but can’t work with Taxonomies; ACT can work with their own Glossaries witch can’t be extended with CustomFields – etc absolutely idiotic restrictions!). Because of that I just amazed that for 20 years 100’000 developers at WP area cannot make not 1 plugin which correctly work with DB Custom Tables… it’s some kind of fantastic flaw beyond any statistics! 🤦🤦🤦

    • This reply was modified 2 years, 10 months ago by johnynla.
    Thread Starter johnynla

    (@johnynla)

    Perhaps another software, such as MS Access, MS Power Apps, or FileMaker for Windows would be a better fit for your needs and expectations.

    Or maybe you’d rather grow corn or milk cows? All jobs have the same number of the main criteria: you can grow corn / you cannot grow corn / how many money does corn brings to you – the same 3 primitive aspects as most WP dev thinking out.

    Thread Starter johnynla

    (@johnynla)

    All these moves only “help to lubricate the wooden wheels of old cart”…

    At 2023 such simple and important functions of your plugin must NOT work so complex and such annoyingly. 🙁

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