Jump to content

requinix

Administrators
  • Content Count

    10,917
  • Joined

  • Last visited

  • Days Won

    198

Posts posted by requinix


  1. When using someone else's libraries, make sure you know what they do.

    .w3-modal{z-index:3;display:none;padding-top:100px;position:fixed;left:0;top:0;width:100%;height:100%;overflow:auto;background-color:rgb(0,0,0);background-color:rgba(0,0,0,0.4)}

    .w3-modal is hidden by default. That means this rule

    div.w3-modal:not(:target) { display: none; }

    which also makes it hidden isn't going to help, and thus has to be inverted to

    div.w3-modal:target { display: block; }

     


  2. Alias it.

    use NotionCommotion\Domain\Entity\Account\Account as EntityAccount;
    use NotionCommotion\Domain\Repository\Account\Account as RepositoryAccount;

    Having an "Account" class inside an "Account" namespace is a separate issue, and I would probably promote it to the Entity/Repository namespace. One of the whole points of namespaces is that you don't have to worry about what classes in other namespaces are called, so don't rename the two Accounts merely because they share an otherwise appropriate name.


  3. For the record, unqualified names (no namespace) like "Account" are always class names, so

    namespace NotionCommotion\Api\Account;
    use NotionCommotion\Domain\Entity\Account\Account;
    class AccountService
    {
        public function read():Account {
            //
        }
    }

    is fine. This also works

    namespace NotionCommotion\Api\Account;
    use NotionCommotion\Domain\Entity\Account;
    class AccountService
    {
        public function read():Account\Account {
            //
        }
    }

    (even if it's starting to look weird) because qualified names like "Account\Account" will never overlap with the current namespace, even if they have the same labels, and it uses the normal resolution rules: since "Account" was use-d, Account\Account resolves to NotionCommotion\Domain\Entity\Account\Account, while if it wasn't use-d then it would be NotionCommotion\Api\Account\Account\Account.


  4. ...oh wait, this code is not located on the page that renders Events.php? Okay, this all makes quite a bit more sense now.

    You can do this showing/hiding stuff with pure CSS, which will also make it work automatically with Events.php#Event1 links.

    Remove all the Javascript that deals with showing and hiding, including the various onclicks, and add a

    <style>
    a.w3-modal:not(:target) { display: none; }
    </style>

    to Events.php. The :target selector is true when you hit anchors like #Event1, so that CSS will hide the w3-modals that are not the current anchor. Which also means going to just Events.php (no anchor) will hide all of them by default.

    • Like 1

  5. If it's not being set automatically, and if

    			$insert_buy = $db->insert('u_paid_videos', [
    				'id_user' => $user_id,
    				'id_video' => $video_id,
    				'session_key' => $_SESSION['session_key'],
    				'video_play_price' => (string)$video_cost, // the cost at the time of purchase // this is the default video cost not the $video_cost_new
    				'video_title' => $video->title, // storing the title
    				'user_id_uploaded' => $video->user_id, // the user who uploaded the video
    				'earned_amount' => $uploader_amount,
    				]);

    you're not setting it either, then of course it'll end up as zero.


  6. What I'm looking for is what your HTML markup looks like after you do

    4 hours ago, Tim32 said:

    Usually I would just add <a href="Events.php#Event2">Event2</a>

    I'm assuming that when you say that, you mean you're setting the href and keeping the onclick. But I don't know what else. So I'd like you to do what you say you would normally do, then post what you end up with that doesn't work.


  7. If it's literally encrypted then who knows. Probably a file-based database system like SQLite, but you'd have to decrypt it.

    If not encrypted then the file extension might be your best bet. Or you can look at the program to see what kinds of libraries it uses and hope it didn't try to roll its own solution.

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.